Triple
T29055200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Urartian cuneiform |
E735366
|
entity |
| Predicate | scriptUser |
P176001
|
FINISHED |
| Object | Urartian kings |
—
|
NE NERFINISHED |
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: Urartian kings | Statement: [Urartian cuneiform, scriptUser, Urartian kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUser Context triple: [Urartian cuneiform, scriptUser, Urartian kings]
-
A.
scriptUserStatus
Indicates the current status or state of a user in relation to a particular script or scripted process.
-
B.
scriptUserCommunity
Indicates a relationship where a user participates in, belongs to, or is associated with a particular community within a script or scripted system.
-
C.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
D.
scriptText
Indicates that one entity contains or represents the textual content of a script associated with another entity.
-
E.
scriptName
Indicates the name or title of a script associated with an entity, typically identifying which script is used, referenced, or executed in a given context.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6db3606808190a80c6e9f5da5b33e |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db1bc348819097c844f76e2fa4fe |
completed | May 3, 2026, 5:20 a.m. |
Created at: April 28, 2026, 10:11 a.m.