Triple
T1163263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lighthouse of Alexandria |
E24539
|
entity |
| Predicate | approximateCompletion |
P22960
|
FINISHED |
| Object | around 280 BC |
—
|
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: around 280 BC | Statement: [Lighthouse of Alexandria, approximateCompletion, around 280 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompletion Context triple: [Lighthouse of Alexandria, approximateCompletion, around 280 BC]
-
A.
completionRate
Indicates the proportion of a task, process, or set of items that has been finished relative to its total intended amount.
-
B.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
C.
approximateYearOfCompletion
chosen
Indicates the estimated calendar year in which something was completed, rather than an exact or confirmed year.
-
D.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
E.
isComplete
Indicates that an action, process, or object has finished all required steps or reached its final state with nothing remaining to be done.
- 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.