Triple
T31472301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CNBC Asia Business Leader Award |
E802890
|
entity |
| Predicate | hasEvaluationMethod |
P750
|
FINISHED |
| Object | editorial selection |
—
|
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: editorial selection | Statement: [CNBC Asia Business Leader Award, hasEvaluationMethod, editorial selection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvaluationMethod Context triple: [CNBC Asia Business Leader Award, hasEvaluationMethod, editorial selection]
-
A.
hasEvaluationType
Indicates that an entity is associated with a specific kind or category of evaluation applied to it.
-
B.
supportsEvaluation
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to be assessed, tested, or evaluated.
-
C.
hasMethodologyProvider
Indicates that one entity serves as the provider or source of the methodology used or applied by another entity.
-
D.
assessmentMethod
chosen
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
hasOutcomeSelectionMethod
Indicates the method or criteria used to select or determine the outcome of a process, event, or decision.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:26 p.m.