Triple
T26990838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prometric |
E679855
|
entity |
| Predicate | technologyEnabled |
P162019
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Prometric, technologyEnabled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyEnabled Context triple: [Prometric, technologyEnabled, true]
-
A.
technologyUse
Indicates the use or application of a particular technology by an entity to perform an action or achieve a purpose.
-
B.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
-
C.
enablesTechnology
Indicates that one entity makes it possible for another entity, system, or process to function through the use or provision of a particular technology.
-
D.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
E.
technologyReadiness
Indicates the level to which a technology has been developed, tested, and proven ready for practical or operational use.
- F. None of above. chosen
Provenance (4 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621c7d3e0819095b1f327637ae4f9 |
completed | May 2, 2026, 4:09 p.m. |
Created at: April 27, 2026, 6:51 a.m.