Triple
T18565769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emerging Issues Task Force (EITF) Issues |
E453755
|
entity |
| Predicate | statusWhenResolved |
P19807
|
FINISHED |
| Object | EITF consensus |
—
|
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: EITF consensus | Statement: [Emerging Issues Task Force (EITF) Issues, statusWhenResolved, EITF consensus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusWhenResolved Context triple: [Emerging Issues Task Force (EITF) Issues, statusWhenResolved, EITF consensus]
-
A.
statusDetermines
Indicates that the status or condition of one entity determines or governs the state, outcome, or behavior of another entity.
-
B.
resolvedIn
chosen
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
statusIncludes
Indicates that one entity’s status set contains or encompasses the status (or statuses) of another entity.
-
E.
statusQuestion
Indicates that one entity asks another about the current state, condition, or situation of something.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afe3ee081909eeee62c889948f4 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.