Triple
T568683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin U-Bahn line U6 |
E13613
|
entity |
| Predicate | openedAsPartially |
P12887
|
FINISHED |
| Object | early 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: early 20th century | Statement: [Berlin U-Bahn line U6, openedAsPartially, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsPartially Context triple: [Berlin U-Bahn line U6, openedAsPartially, early 20th century]
-
A.
openedInPart
chosen
Indicates that an entity was opened or made accessible only partially, rather than fully or completely.
-
B.
openedAs
Indicates that one entity began operating, functioning, or being available to the public under the form, name, or role of another entity.
-
C.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
openedAsPartOfProject
Indicates that something was opened or initiated as a component or phase of a specific project.
-
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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b0406d481908af5fc7bc67103fb |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.