Triple
T31946920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horizon |
E815675
|
entity |
| Predicate | worldFeature |
P169885
|
FINISHED |
| Object | tribal human societies |
—
|
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: tribal human societies | Statement: [Horizon, worldFeature, tribal human societies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldFeature Context triple: [Horizon, worldFeature, tribal human societies]
-
A.
featuresWorld
chosen
Indicates that something (such as a work, product, or system) includes, depicts, or is set within a particular world or environment.
-
B.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
-
C.
politicalFeature
Indicates that an entity possesses a political characteristic, attribute, or aspect relevant to governance, power structures, or public policy.
-
D.
inWorldGeography
Indicates that something is located within or belongs to the physical geography of the world (such as a region, landscape, or geographic setting).
-
E.
territoryFeature
Indicates that a specific geographic or physical feature is located within, characterizes, or is part of a given territory.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 12:07 a.m.