Triple
T8683081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dmanisi |
E206084
|
entity |
| Predicate | notableSkullDesignation |
P84470
|
FINISHED |
| Object | D2700 |
—
|
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: D2700 | Statement: [Dmanisi, notableSkullDesignation, D2700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSkullDesignation Context triple: [Dmanisi, notableSkullDesignation, D2700]
-
A.
notableQuarry
Indicates that an entity is a quarry that is particularly significant, well-known, or noteworthy in some context.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableRelic
Indicates that an entity is a historically or culturally significant relic associated with another entity (such as a place, person, or event).
-
D.
notableSculpture
Indicates that an entity is a sculpture for which the subject is especially known or recognized.
-
E.
notableGiant
Indicates that an entity is recognized as a giant of particular note, standing out for its exceptional size, influence, or significance relative to others of its kind.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae9da3c8190866e24970a7aeba3 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc4ae517108190a71a86349815f4ce |
completed | March 31, 2026, 10:29 p.m. |
Created at: March 30, 2026, 6:32 p.m.