Triple
T1893128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cardinal (train) |
E41916
|
entity |
| Predicate | transportDomain |
P32899
|
FINISHED |
| Object | rail transport |
—
|
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: rail transport | Statement: [Cardinal (train), transportDomain, rail transport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportDomain Context triple: [Cardinal (train), transportDomain, rail transport]
-
A.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
B.
inputDomain
Indicates that a function, process, or system accepts inputs belonging to a specified domain or set of allowable values.
-
C.
regulatoryDomain
Indicates that one entity defines or governs the rules, policies, or constraints under which another entity must operate.
-
D.
sharesDomainWith
Indicates that two entities operate within, belong to, or are associated with the same domain or domain-like scope.
-
E.
transferredRegion
Indicates that control, ownership, or responsibility for a geographic or administrative region has been moved from one entity to another.
- F. None of above. chosen
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_69a8864b6de0819098d089f6a1b910a7 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1480a6c81909fcf5cce4c42fed4 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb09b27e88190bff164040fef6d7e |
completed | March 7, 2026, 4:59 a.m. |
Created at: March 4, 2026, 7:34 p.m.