Triple
T874780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reporters Without Borders |
E18892
|
entity |
| Predicate | operatesWorldwide |
P1381
|
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: [Reporters Without Borders, operatesWorldwide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesWorldwide Context triple: [Reporters Without Borders, operatesWorldwide, true]
-
A.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
-
B.
operatesToContinents
Indicates that an entity conducts or provides operations or services that extend across or are directed toward multiple continents.
-
C.
hasGlobalReach
chosen
Indicates that an entity’s influence, operations, or impact extends across multiple countries or worldwide.
-
D.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
E.
operatesOver
Indicates that one entity performs actions or exerts functional control across, upon, or throughout another entity or domain.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4acae12948190923d31966c26a130 |
completed | March 1, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69a4aa8b9b5c81909ac71904f8b8b5cd |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.