Triple
T15666087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Area |
E377190
|
entity |
| Predicate | purposeOfRegime |
P119667
|
FINISHED |
| Object | benefit of humankind as a whole |
—
|
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: benefit of humankind as a whole | Statement: [the Area, purposeOfRegime, benefit of humankind as a whole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purposeOfRegime Context triple: [the Area, purposeOfRegime, benefit of humankind as a whole]
-
A.
regimeDescription
Indicates that an entity provides a textual characterization or explanation of a particular regime, system, or governing arrangement.
-
B.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
C.
targetedRegime
Indicates that an entity intentionally directed actions, policies, or operations against a particular governing regime.
-
D.
regimeName
Indicates that a particular name or label is assigned to a specific regime.
-
E.
sovereigntyRegime
Indicates the type or structure of political authority and control exercised over a territory or population.
- F. None of above. chosen
Provenance (4 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f0f4df08190ad2c5d78e435d8eb |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:16 a.m.