Triple
T2996388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camp Griffiss |
E81078
|
entity |
| Predicate | endUseDate |
P6544
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Camp Griffiss, endUseDate, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endUseDate Context triple: [Camp Griffiss, endUseDate, 1945]
-
A.
usedUntil
chosen
Indicates that something remained in use or operation up to a specified time or event, after which it was no longer used.
-
B.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
C.
reconstitutionDate
Indicates the date on which something (typically a substance, solution, or entity) is restored or prepared from a prior, preserved, or inactive state.
-
D.
startUseBy
Indicates the point in time from which an entity begins to be used by another entity or for a particular purpose.
-
E.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99f481688190ae8cd1e057f9dfc7 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.