Triple
T14218512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Philanthropist |
E352423
|
entity |
| Predicate | hasSettingScope |
P397
|
FINISHED |
| Object | international locations |
—
|
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: international locations | Statement: [The Philanthropist, hasSettingScope, international locations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingScope Context triple: [The Philanthropist, hasSettingScope, international locations]
-
A.
hasScope
chosen
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
B.
hasSetting
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
C.
hasSettingRole
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
D.
hasScopeRule
Indicates that a given entity is governed, constrained, or interpreted according to a particular scope-defining rule.
-
E.
hasSettingSymbol
Indicates that one entity uses or is associated with another entity as a symbolic representation of its setting or environment.
- 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de621258d4819085f358cd2cf109e4 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:06 a.m.