Triple
T1163250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lighthouse of Alexandria |
E24539
|
entity |
| Predicate | usedLightSource |
P5496
|
FINISHED |
| Object | fire |
—
|
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: fire | Statement: [Lighthouse of Alexandria, usedLightSource, fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedLightSource Context triple: [Lighthouse of Alexandria, usedLightSource, fire]
-
A.
lightSourceFor
chosen
Indicates that one entity serves as the source of illumination for another entity.
-
B.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
-
C.
lightPath
Indicates the route or trajectory that light follows as it travels between entities or through a medium.
-
D.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
E.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcc9dc5081908e225a485186ab12 |
completed | March 1, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.