Triple
T23234053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Búhos (night owl buses) |
E581237
|
entity |
| Predicate | ticketCompatibility |
P5883
|
FINISHED |
| Object | compatible with standard Madrid bus tickets and passes |
—
|
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: compatible with standard Madrid bus tickets and passes | Statement: [Búhos (night owl buses), ticketCompatibility, compatible with standard Madrid bus tickets and passes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketCompatibility Context triple: [Búhos (night owl buses), ticketCompatibility, compatible with standard Madrid bus tickets and passes]
-
A.
ticketingCompatibleWith
chosen
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
B.
compatibleSign
Indicates that two entities are considered astrologically harmonious or well-matched based on their zodiac signs.
-
C.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
-
D.
formatCompatibleWith
Indicates that one format can be correctly used, interpreted, or processed in conjunction with another format without conflict or loss of information.
-
E.
claimsCompatibilityWith
Indicates that one entity asserts it is compatible or can work harmoniously with another entity.
- 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_69e2460556f88190be1744a84a84173f |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f192e7bed88190b914b238c5f49860 |
completed | April 29, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:09 p.m.