Triple
T23744698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clash of Civilizations |
E586781
|
entity |
| Predicate | definesKeyUnitAs |
P153535
|
FINISHED |
| Object | civilization |
—
|
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: civilization | Statement: [Clash of Civilizations, definesKeyUnitAs, civilization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesKeyUnitAs Context triple: [Clash of Civilizations, definesKeyUnitAs, civilization]
-
A.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
B.
definedInUnit
Indicates that something (such as a symbol, element, or construct) is declared or established within a particular unit, module, or file.
-
C.
confirmedDefinitionOfUnit
Indicates that an authoritative or validated specification has been established for the meaning, measurement, or usage of a particular unit.
-
D.
standardUnitRelation
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard unit.
-
E.
integerUnit
Indicates that one entity serves as the integer-valued unit or base measurement associated with another entity.
- 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_69e24908efb08190bf755c3a9b91f222 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcbcc4f88190a00fceeafbfb5cfd |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:12 p.m.