Triple
T1702334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life on Land |
E36793
|
entity |
| Predicate | isGlobalInScope |
P28485
|
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: [Life on Land, isGlobalInScope, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGlobalInScope Context triple: [Life on Land, isGlobalInScope, true]
-
A.
isGlobalScope
chosen
Indicates that something exists or applies at the global scope, rather than being limited to a local or nested context.
-
B.
hasScope
Indicates that one entity defines, limits, or encompasses the range, extent, or applicability within which another entity operates or is valid.
-
C.
scopeOfDeclaration
Indicates the syntactic region or context within which a particular declaration is valid and can be referenced.
-
D.
isIntrinsic
Indicates that a property or characteristic belongs inherently to an entity and does not depend on external conditions or relations.
-
E.
isGloballySignificant
Indicates that something has importance, impact, or relevance on a worldwide scale rather than being limited to a local or regional context.
- 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_69a886163dec8190859c514232a37a05 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf169da888190b3aa334752f1952b |
completed | March 6, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69aa61b8ce348190b46154af0b041ff0 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.