Triple
T4608108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loop 202 |
E100485
|
entity |
| Predicate | openingCompleted |
P617
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Loop 202, openingCompleted, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingCompleted Context triple: [Loop 202, openingCompleted, 2020]
-
A.
openedAfter
Indicates that one entity was opened at a later time than another entity.
-
B.
openedIn
chosen
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
C.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
D.
openedSegment
Indicates that one entity has initiated or created a new segment, section, or interval within another entity or process.
-
E.
opened
Indicates that one entity caused another entity (such as an object, container, or passage) to change from a closed or inaccessible state to an open or accessible state.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd599debdc81909d11d0e871c666bb |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.