Triple
T28005796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF participants |
E707270
|
entity |
| Predicate | followPrinciple |
P47536
|
FINISHED |
| Object | individual participation |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: individual participation | Statement: [IETF participants, followPrinciple, individual participation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followPrinciple Context triple: [IETF participants, followPrinciple, individual participation]
-
A.
principle1
Indicates that one entity serves as a primary rule, guideline, or foundational principle governing or guiding another entity.
-
B.
principle7
Indicates that an entity is associated with, governed by, or exemplifies the seventh principle in a defined set of principles.
-
C.
principle6
Indicates that one entity upholds, follows, or is governed by a specific sixth principle in a defined set of principles.
-
D.
principle4
Indicates that an entity embodies, adheres to, or is governed by a specific fourth principle within a defined set of principles.
-
E.
implementsPrinciple
chosen
Indicates that an entity applies, follows, or puts into practice a specified principle in its design, behavior, or operation.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 8 p.m.