Triple
T787483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient Near East collection |
E16836
|
entity |
| Predicate | containsObjectType |
P121
|
FINISHED |
| Object | cuneiform tablet |
—
|
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: cuneiform tablet | Statement: [Ancient Near East collection, containsObjectType, cuneiform tablet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsObjectType Context triple: [Ancient Near East collection, containsObjectType, cuneiform tablet]
-
A.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
-
B.
hasStructureType
Indicates that an entity possesses or is classified by a specific structural type or configuration.
-
C.
hasMemberType
chosen
Indicates that an entity includes or is associated with members belonging to a specified type or category.
-
D.
canBeTypeOf
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
E.
hasCollectionType
Indicates that an entity is associated with or organized under a specific type or category of collection.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a78171908190a38a70274bfbebf9 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a50ef72c819084ffe9f31dbd0262 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:38 p.m.