Triple
T3081851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IETF working groups |
E64275
|
entity |
| Predicate | lifecycleStage |
P8338
|
FINISHED |
| Object | proposed |
—
|
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: proposed | Statement: [IETF working groups, lifecycleStage, proposed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleStage Context triple: [IETF working groups, lifecycleStage, proposed]
-
A.
lifecycleStatus
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
B.
coversLifecycleStage
Indicates that one entity includes, addresses, or spans a particular stage within a defined lifecycle.
-
C.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
D.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
E.
lifeStage
chosen
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1e70b9081908c801d084a6ae992 |
completed | March 8, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.