Triple
T1163256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lighthouse of Alexandria |
E24539
|
entity |
| Predicate | destructionPeriod |
P11080
|
FINISHED |
| Object | between 10th and 14th centuries AD |
—
|
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: between 10th and 14th centuries AD | Statement: [Lighthouse of Alexandria, destructionPeriod, between 10th and 14th centuries AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destructionPeriod Context triple: [Lighthouse of Alexandria, destructionPeriod, between 10th and 14th centuries AD]
-
A.
demolitionPeriod
chosen
Indicates the time span during which the demolition of an entity or structure takes place.
-
B.
dateDestroyed
Indicates the specific date on which an entity was destroyed or ceased to exist.
-
C.
destroyedDuring
Indicates that one entity was destroyed in the course of, or as a consequence of, a specified event or time period.
-
D.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
E.
expirationPolicy
Indicates the rules or conditions under which something becomes invalid, unusable, or no longer in effect after a certain time or event.
- 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.