Triple
T19186677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | planetary boundaries framework |
E469719
|
entity |
| Predicate | proposesNumberOfBoundaries |
P134777
|
FINISHED |
| Object | 9 |
—
|
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: 9 | Statement: [planetary boundaries framework, proposesNumberOfBoundaries, 9]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesNumberOfBoundaries Context triple: [planetary boundaries framework, proposesNumberOfBoundaries, 9]
-
A.
showsBoundaries
Indicates that one entity visually or conceptually delineates the limits, edges, or extents of another entity.
-
B.
numberOfProvinces
Indicates the total count of provinces associated with a given entity or within a specified region or country.
-
C.
boundariesInForceSinceElection
Indicates that the current boundaries have been in effect continuously since the specified election.
-
D.
hasDefinedBoundaries
Indicates that the entity possesses clearly established and recognized limits or borders that distinguish it from its surroundings or from other entities.
-
E.
hasNumberOfConstituencies
Indicates the specific count of constituencies associated with an entity.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f620f1f08190a0daaf0d1483d724 |
completed | April 20, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.