Triple
T4351899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nol Red Ticket |
E98044
|
entity |
| Predicate | topUpLocation |
P27918
|
FINISHED |
| Object | Dubai Metro ticket machines |
—
|
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: Dubai Metro ticket machines | Statement: [Nol Red Ticket, topUpLocation, Dubai Metro ticket machines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topUpLocation Context triple: [Nol Red Ticket, topUpLocation, Dubai Metro ticket machines]
-
A.
topUpLocations
chosen
Indicates locations where a balance, credit, or value can be increased or recharged for a related account, service, or device.
-
B.
topUpMethod
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
C.
topLocation
Indicates that one location is the primary, highest-level, or most prominent place associated with another entity or set of locations.
-
D.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
E.
connectsLocation
Indicates a relationship where one entity serves as a link or route that joins or provides access between two locations.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.