Triple
T28376950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grizzly Peak Airfield |
E718778
|
entity |
| Predicate | openingDateAsCondorFlats |
P170662
|
FINISHED |
| Object | 2001-02-08 |
—
|
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: 2001-02-08 | Statement: [Grizzly Peak Airfield, openingDateAsCondorFlats, 2001-02-08]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingDateAsCondorFlats Context triple: [Grizzly Peak Airfield, openingDateAsCondorFlats, 2001-02-08]
-
A.
expansionOpeningDate
Indicates the date on which an expansion of something (such as a facility, service, or project) was officially opened or became operational.
-
B.
openHouseStartDate
Indicates the calendar date on which an open house event for a property is scheduled to begin.
-
C.
relocationOpeningDate
Indicates the date on which a relocation (such as a move or transfer to a new place) is officially opened or becomes effective.
-
D.
openingDateApproximate
Indicates that the date when something was opened or began is not known exactly and is only an approximate value.
-
E.
plannedOpeningDate
Indicates the date on which something is scheduled or intended to begin operating or become available.
- 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_69eff6ee5afc8190bd7375a29f0cc6c6 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f693ffa7908190aa4c451b16df9be6 |
completed | May 3, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 28, 2026, 1:03 a.m.