Triple
T192412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ALICE |
E3748
|
entity |
| Predicate | collisionSystem |
P5341
|
FINISHED |
| Object | lead–lead |
—
|
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: lead–lead | Statement: [ALICE, collisionSystem, lead–lead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionSystem Context triple: [ALICE, collisionSystem, lead–lead]
-
A.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
-
B.
partOfSystem
Indicates that one entity functions as a component or subsystem within the structure or organization of another entity.
-
C.
system
Indicates that an entity functions as or belongs to a structured, organized set of components or processes that operate together as a system.
-
D.
overlapsWith
Indicates that two entities share a common part or region in space, time, or extent, but neither is completely contained within the other.
-
E.
involvesProjectile
Indicates that the action or event includes the use, presence, or motion of a projectile as a key component of the interaction between entities.
- F. None of above. chosen
Provenance (4 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_69a2548debd48190ae3a06d6e65b53c6 |
completed | Feb. 28, 2026, 2:35 a.m. |
| NER | Named-entity recognition | batch_69a259669ba08190a5be1d2e10e70b27 |
completed | Feb. 28, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69a2567567508190b3a41329a15c7156 |
completed | Feb. 28, 2026, 2:44 a.m. |
| PDg | Predicate description generation | batch_69a25710bdfc81909b6697159104cf53 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:41 a.m.