Triple
T4377093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gothia Cup |
E99032
|
entity |
| Predicate | transportModel |
P36833
|
FINISHED |
| Object | tournament transport card for public transit |
—
|
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: tournament transport card for public transit | Statement: [Gothia Cup, transportModel, tournament transport card for public transit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModel Context triple: [Gothia Cup, transportModel, tournament transport card for public transit]
-
A.
transportType
Indicates the mode or means of transportation used in carrying something or someone from one place to another.
-
B.
transports
Indicates that one entity carries or conveys another entity from one place to another.
-
C.
transportationFunction
Indicates that one entity serves to move or carry another entity from one place to another.
-
D.
primaryTransportModel
chosen
Indicates that one transport model is designated as the main or default model used for a given context or entity.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523ed220819090cef1a7933489d9 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.