Triple
T25758768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titti |
E648675
|
entity |
| Predicate | civilizationStage |
P56099
|
FINISHED |
| Object | tribal society |
—
|
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 society | Statement: [Titti, civilizationStage, tribal society]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilizationStage Context triple: [Titti, civilizationStage, tribal society]
-
A.
civilization
Indicates that an entity is a civilization, i.e., a complex, organized human society characterized by structured institutions, culture, and social systems.
-
B.
laterCivilization
Indicates that one civilization arose or existed chronologically after another civilization.
-
C.
coreCivilization
Indicates that an entity functions as a central or foundational civilization within a broader cultural, historical, or systemic context.
-
D.
hasCivilization
Indicates that an entity possesses, hosts, or is associated with an organized society or culture characterized by social, political, and technological development.
-
E.
describesCivilizationType
chosen
Indicates that one entity characterizes or specifies the type or category of civilization to which another entity belongs.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd847ee48190a32b6b618d66f22d |
completed | May 2, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 4:43 a.m.