Triple
T18761751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olivet |
E458784
|
entity |
| Predicate | reopenedWithAngelsFlight |
P59082
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Olivet, reopenedWithAngelsFlight, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopenedWithAngelsFlight Context triple: [Olivet, reopenedWithAngelsFlight, 2017]
-
A.
reopenedAsTheater
Indicates that a venue or building, previously closed or used differently, has been opened again specifically to function as a theater.
-
B.
reopenedFor
chosen
Indicates that an entity, previously closed or inactive, has been opened again to allow access, use, or operation for another entity or purpose.
-
C.
reopenedAsPartOf
Indicates that an entity was reopened as a component or phase within a larger, ongoing process, case, or activity.
-
D.
reopenedAfter
Indicates that an entity was closed or inactive and then opened or made active again following a specified prior event or time.
-
E.
reopensIn
Indicates that an entity resumes operation or becomes accessible again at a specified time or under specified conditions after having been closed or inactive.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d7fd5008190823bc7e37fdd6669 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.