Triple
T33106744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsingtau |
E847208
|
entity |
| Predicate | railwayBuiltBy |
P78309
|
FINISHED |
| Object | German Empire |
—
|
NE NERFINISHED |
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: German Empire | Statement: [Tsingtau, railwayBuiltBy, German Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railwayBuiltBy Context triple: [Tsingtau, railwayBuiltBy, German Empire]
-
A.
railwayConstructedIn
Indicates that a railway was built or established within a specified location or during a specified time period.
-
B.
railwayBuiltFor
Indicates that a railway was constructed to serve, support, or provide access to a particular entity or purpose.
-
C.
railLineBuiltBy
chosen
Indicates that a particular rail line was constructed or developed by a specified agent, such as a company, organization, or authority.
-
D.
railwayDevelopedBy
Indicates that a railway was planned, constructed, or otherwise brought into existence through the efforts or initiative of a particular developer or organization.
-
E.
formedByRailroad
Indicates that something (such as a route, boundary, or structure) is created, defined, or constituted by a railroad or railway line.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: May 1, 2026, 1:26 a.m.