Triple
T37689595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anlamani |
E938466
|
entity |
| Predicate | neighboringCivilization |
P11274
|
FINISHED |
| Object | Ancient Egypt |
—
|
NE NERFINISHED |
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: Ancient Egypt | Statement: [Anlamani, neighboringCivilization, Ancient Egypt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neighboringCivilization Context triple: [Anlamani, neighboringCivilization, Ancient Egypt]
-
A.
coreCivilization
Indicates that an entity functions as a central or foundational civilization within a broader cultural, historical, or systemic context.
-
B.
neighboringPeoples
chosen
Indicates that two peoples or ethnic groups live in adjacent or nearby territories, sharing a common border or close geographic proximity.
-
C.
affectedCivilization
Indicates that one civilization has experienced an impact, influence, or change as a result of another entity, event, or process.
-
D.
laterCivilization
Indicates that one civilization arose or existed chronologically after another civilization.
-
E.
civilization
Indicates that an entity is a civilization, i.e., a complex, organized human society characterized by structured institutions, culture, and social systems.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.