Triple
T4772249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NoVo Foundation |
E105955
|
entity |
| Predicate | worksInRegion |
P6665
|
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: [NoVo Foundation, worksInRegion, global]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worksInRegion Context triple: [NoVo Foundation, worksInRegion, global]
-
A.
operatedInRegion
chosen
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
employerInRegion
Indicates that an employer operates or has its primary business presence within a specified geographic region.
-
C.
serviceRegion
Indicates the geographic area or jurisdiction within which a service is provided or applicable.
-
D.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
-
E.
hasHeadquartersInRegion
Indicates that an organization’s main administrative or corporate headquarters is located within a specified geographic region.
- 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_69bd43f226fc8190b867cc249c2a9042 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd655f98b0819088c05c5502ecf2cd |
completed | March 20, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69bd6229d8448190a271719e5e30fd82 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.