Triple
T14538240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GlobalPlatform |
E341106
|
entity |
| Predicate | definesSpecificationFor |
P21520
|
FINISHED |
| Object | smart cards |
—
|
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: smart cards | Statement: [GlobalPlatform, definesSpecificationFor, smart cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSpecificationFor Context triple: [GlobalPlatform, definesSpecificationFor, smart cards]
-
A.
specifiedFor
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
B.
hasSpecification
Indicates that an entity is associated with a particular specification that defines or constrains its properties, behavior, or requirements.
-
C.
roleInSpecification
Indicates that an entity participates in a specification with a particular role or function within that specification.
-
D.
specType
Indicates the specific type or category of a specification that an entity is associated with.
-
E.
designSpecifiedBy
chosen
Indicates that the design or specification of one entity is defined, authored, or determined by 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bb90008190947ac0961393446d |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.