Triple
T19093241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SL fare system |
E467340
|
entity |
| Predicate | dataFormatUsed |
P109452
|
FINISHED |
| Object | contactless smart card technology |
—
|
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 technology | Statement: [SL fare system, dataFormatUsed, contactless smart card technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataFormatUsed Context triple: [SL fare system, dataFormatUsed, contactless smart card technology]
-
A.
storageFormat
Indicates the specific way in which data or content is physically or logically organized, encoded, and stored.
-
B.
usedFormat
chosen
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
C.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
D.
draftFormatUsed
Indicates that a particular draft was created or prepared using a specified format.
-
E.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e34cf5e481908e1f180dacd5602f |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.