Triple
T24874779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Hague bus network |
E622536
|
entity |
| Predicate | typicalTicketMedium |
P42387
|
FINISHED |
| Object | contactless smart card |
—
|
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: contactless smart card | Statement: [The Hague bus network, typicalTicketMedium, contactless smart card]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalTicketMedium Context triple: [The Hague bus network, typicalTicketMedium, contactless smart card]
-
A.
ticketMediumType
chosen
Indicates the type or format of the medium through which a ticket is issued, stored, or presented (e.g., paper, mobile, electronic).
-
B.
typicalTicketText
Indicates that the associated text represents the standard or commonly used wording for a ticket.
-
C.
typicalBillet
Indicates that something serves as a standard or characteristic billet or assignment for a given role, context, or entity.
-
D.
ticketTypeCommon
Indicates that two or more tickets share the same general type or classification.
-
E.
stratotypeMedium
Indicates the type of material or medium (e.g., rock, sediment) that serves as the reference standard for a stratigraphic unit or stratotype.
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 18, 2026, 5:23 a.m.