Triple
T1096734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCIceCandidate |
E24286
|
entity |
| Predicate | lifecycleEvent |
P12444
|
FINISHED |
| Object | generatedDuringICEGathering |
—
|
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: generatedDuringICEGathering | Statement: [RTCIceCandidate, lifecycleEvent, generatedDuringICEGathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleEvent Context triple: [RTCIceCandidate, lifecycleEvent, generatedDuringICEGathering]
-
A.
lifeCycle
chosen
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
B.
launchEvent
Indicates an event in which something is formally initiated, introduced, or set into operation.
-
C.
fireEvent
Indicates triggering or initiating a specific event or action within a system or process.
-
D.
parentEvent
Indicates that one event serves as the higher-level or originating event from which another event is derived, contained, or logically dependent.
-
E.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b99ffb3481908cd168b6c58e1c6d |
completed | March 1, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69a4b7448c148190a3c9a4158ebd05b4 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.