Triple
T12669880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El-Auria |
E302648
|
entity |
| Predicate | civilizationTrait |
P106203
|
FINISHED |
| Object | non-aggressive |
—
|
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: non-aggressive | Statement: [El-Auria, civilizationTrait, non-aggressive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilizationTrait Context triple: [El-Auria, civilizationTrait, non-aggressive]
-
A.
coreCivilization
Indicates that an entity functions as a central or foundational civilization within a broader cultural, historical, or systemic context.
-
B.
describesCivilizationType
Indicates that one entity characterizes or specifies the type or category of civilization to which another entity belongs.
-
C.
affectedCivilization
Indicates that one civilization has experienced an impact, influence, or change as a result of another entity, event, or process.
-
D.
focusesOnCivilization
Indicates that an entity’s primary subject, concern, or activity is centered on a particular civilization or civilizations.
-
E.
hasCivilization
Indicates that an entity possesses, hosts, or is associated with an organized society or culture characterized by social, political, and technological development.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960bb64ec8190bd0400cf0cc8b0a7 |
completed | April 10, 2026, 8:42 p.m. |
| PDg | Predicate description generation | batch_69d961acadb8819098de743bc951fedb |
completed | April 10, 2026, 8:46 p.m. |
Created at: April 9, 2026, 5:20 p.m.