Triple
T7514243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yerebatan Sarnıcı |
E177598
|
entity |
| Predicate | reopeningToPublic |
P77405
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Yerebatan Sarnıcı, reopeningToPublic, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reopeningToPublic Context triple: [Yerebatan Sarnıcı, reopeningToPublic, 20th century]
-
A.
reopeningDate
Indicates the date on which something that was previously closed is opened again for use or access.
-
B.
reopeningAs
Indicates that an entity that was previously closed or inactive is starting operations again under a new or updated form, identity, or function.
-
C.
reopeningPattern
Indicates a recurring or structured way in which something that was previously closed or inactive is opened or resumed again over time.
-
D.
reopeningPerformance
Indicates the performance or outcome associated with resuming or restarting an activity, operation, or service after it has been closed or suspended.
-
E.
openedForPublic
Indicates that something has been made accessible or available for use, entry, or participation by the general public.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5d6ccb08190a568a9b58bfbd0cc |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:45 p.m.