Triple
T31329154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigo travel card |
E798976
|
entity |
| Predicate | canBeLoadedVia |
P127767
|
FINISHED |
| Object | smartphone NFC applications |
—
|
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: smartphone NFC applications | Statement: [Navigo travel card, canBeLoadedVia, smartphone NFC applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeLoadedVia Context triple: [Navigo travel card, canBeLoadedVia, smartphone NFC applications]
-
A.
canBeLoadedBy
chosen
Indicates that one entity is capable of being loaded, initialized, or brought into use by another entity.
-
B.
canBeLoadedAt
Indicates that an entity is capable of being placed onto or into another entity (such as a vehicle, container, or system) at a specific location or point in time.
-
C.
supportsDynamicLoading
Indicates that an entity is capable of loading components or resources at runtime rather than only at startup or compile time.
-
D.
canBeDeployedUnder
Indicates that one entity is permitted or suitable to be deployed or operated under the conditions, context, or authority defined by another entity.
-
E.
canBeReadWith
Indicates that one entity is suitable or compatible to be read or interpreted together 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: April 29, 2026, 9:16 p.m.