Triple
T38575260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LLD |
E929382
|
entity |
| Predicate | historicalCodeFor |
P28337
|
FINISHED |
| Object | Lydda Airport |
E272665
|
NE 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: Lydda Airport | Statement: [LLD, historicalCodeFor, Lydda Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalCodeFor Context triple: [LLD, historicalCodeFor, Lydda Airport]
-
A.
historicalFunction
Indicates the role, purpose, or activity an entity had during a past period or in a historical context.
-
B.
historicalRegionCode
chosen
Indicates that an entity is associated with a specific code identifying a historical region.
-
C.
historicalVersion
Indicates that one entity represents an earlier or past version in the history or evolution of another entity.
-
D.
historicallyImplementedAs
Indicates that one entity was used or realized as another entity in the past, even if that is no longer the case.
-
E.
historicalMethod
Indicates that a particular method, approach, or technique was used in the past, typically in a historical context or during a previous period of activity.
- F. None of above.
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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a02f847b9848190a9fedbc411ae0918 |
completed | May 12, 2026, 9:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41fd4ca3648190a4e1fb5434f194a8 |
completed | June 29, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_6a02f556860c8190b2995433fa05fdd0 |
completed | May 12, 2026, 9:39 a.m. |
Created at: May 3, 2026, 4:32 p.m.