Triple
T19147004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stubenring |
E468704
|
entity |
| Predicate | wasCreatedAsPartOf |
P35910
|
FINISHED |
| Object | 19th-century Ringstrasse project |
—
|
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: 19th-century Ringstrasse project | Statement: [Stubenring, wasCreatedAsPartOf, 19th-century Ringstrasse project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCreatedAsPartOf Context triple: [Stubenring, wasCreatedAsPartOf, 19th-century Ringstrasse project]
-
A.
builtAsPartOf
chosen
Indicates that one entity was constructed as a component or subset of a larger, encompassing entity or project.
-
B.
usedToBePartOf
Indicates that an entity was formerly a component or member of another entity but is no longer part of it.
-
C.
reconstructedAsPartOf
Indicates that one entity has been rebuilt, restored, or recreated as a component or segment of another, larger whole.
-
D.
raisedAsPartOf
Indicates that an entity was brought up, nurtured, or developed within the context, environment, or membership of another entity or group.
-
E.
adoptedAsPartOf
Indicates that one entity has been taken in, integrated, or accepted as a component or member within another entity or larger whole.
- 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_69d8dd084ff48190ac0f8c46ee722629 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e97a79a48190b243553023bf9081 |
completed | April 20, 2026, 8:53 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b475d88190a8c15e8eb01dbfef |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.