Triple
T570298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thomson Reuters |
E13647
|
entity |
| Predicate | scopeOfOperation |
P6851
|
FINISHED |
| Object | global |
—
|
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: global | Statement: [Thomson Reuters, scopeOfOperation, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfOperation Context triple: [Thomson Reuters, scopeOfOperation, global]
-
A.
operationalScope
chosen
Indicates the range, extent, or boundaries within which an entity, process, or activity is authorized or designed to operate.
-
B.
scopeOfUse
Indicates the range, context, or conditions under which something is intended, allowed, or applicable to be used.
-
C.
scopeOfContribution
Indicates the specific area, domain, or extent within which an entity’s contribution or involvement applies.
-
D.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
E.
missionScope
Indicates the defined range, objectives, and boundaries within which a mission or operation is intended to be carried out.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b057e708190b4e5975516e58993 |
completed | March 1, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.