Triple
T30168802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fara (ancient Shuruppak) |
E766862
|
entity |
| Predicate | hasScriptPhase |
P182252
|
FINISHED |
| Object | archaic cuneiform |
—
|
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: archaic cuneiform | Statement: [Fara (ancient Shuruppak), hasScriptPhase, archaic cuneiform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScriptPhase Context triple: [Fara (ancient Shuruppak), hasScriptPhase, archaic cuneiform]
-
A.
hasScriptStatus
Indicates that an entity has a particular script-related state or condition, such as whether a script is present, active, or in a given status.
-
B.
hasScriptScope
Indicates that something is associated with, defined within, or limited to a particular script’s scope or execution context.
-
C.
hasScriptCode
Indicates that an entity is associated with a particular writing system identified by a specific script code.
-
D.
hasScriptRegulator
Indicates that an entity has an associated mechanism or component that controls or governs its script or scripting behavior.
-
E.
hasScriptCodeStatus
Indicates the status or condition assigned to a script code within a given coding or classification system.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 29, 2026, 7:24 p.m.