Triple
T35107790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Südbahn railway line |
E1013199
|
entity |
| Predicate | originalEndPoint |
P885
|
FINISHED |
| Object | Trieste |
E4389
|
NE 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: Trieste | Statement: [Südbahn railway line, originalEndPoint, Trieste]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEndPoint Context triple: [Südbahn railway line, originalEndPoint, Trieste]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
originalDestination
chosen
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
-
C.
secondaryEndpoint
Indicates that something serves as an additional, non-primary endpoint or target associated with a main endpoint in a relationship or process.
-
D.
startPoint
Indicates the initial location or position from which an object, path, or action begins.
-
E.
primaryRouteEnd
Indicates the endpoint location at which a primary route or main path terminates.
- F. None of above.
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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37cffac58481909a973bf9513a4011 |
completed | June 21, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.