Triple
T16774345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linear Elamite |
E407682
|
entity |
| Predicate | hasSignInventorySize |
P89666
|
FINISHED |
| Object | about 80–100 signs |
—
|
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: about 80–100 signs | Statement: [Linear Elamite, hasSignInventorySize, about 80–100 signs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSignInventorySize Context triple: [Linear Elamite, hasSignInventorySize, about 80–100 signs]
-
A.
hasSignInventory
chosen
Indicates that an entity possesses or is associated with a specific set or collection of signs used within a writing or symbolic system.
-
B.
hasSize
Indicates that one entity possesses a particular physical magnitude or extent, such as length, volume, or overall dimensions.
-
C.
hasSign
Indicates that an entity possesses, displays, or is associated with a particular sign or symbol.
-
D.
hasInventorySystem
Indicates that an entity possesses or utilizes a system for tracking, managing, and controlling its inventory.
-
E.
hasLotSize
Indicates that an entity possesses a specific amount or extent of physical area, typically referring to the size of a parcel of land or property lot.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b038d0608190be15c758427bb664 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.