Triple
T3561768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sde Dov Airport |
E75353
|
entity |
| Predicate | redevelopmentFor |
P50376
|
FINISHED |
| Object | residential construction |
—
|
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: residential construction | Statement: [Sde Dov Airport, redevelopmentFor, residential construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redevelopmentFor Context triple: [Sde Dov Airport, redevelopmentFor, residential construction]
-
A.
reopenedAfterRedevelopment
Indicates that a place or facility was closed for redevelopment and subsequently opened again once the redevelopment was completed.
-
B.
redevelopmentStartDate
Indicates the date on which a redevelopment project or process officially begins.
-
C.
urbanRedevelopmentArea
Indicates that a location is designated for concentrated urban renewal activities such as redevelopment, revitalization, or land-use transformation.
-
D.
redevelopmentPartner
Indicates that one entity collaborates with or is designated to work with another entity as a partner in a redevelopment project or process.
-
E.
reconstructionFor
Indicates that one entity serves as a reconstruction, restoration, or rebuilt version of another entity.
- 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_69ad85d45090819086f34fb85d850a1e |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc08bdde88190915d2f6ddf26e00e |
completed | March 8, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69adb834779081908468e182d5f6cf02 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb9bbb62c8190989629ca11733e1b |
completed | March 8, 2026, 6:02 p.m. |
Created at: March 8, 2026, 3:21 p.m.