Triple
T25458688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepherites I |
E637982
|
entity |
| Predicate | scriptUsedInMonuments |
P159127
|
FINISHED |
| Object | hieroglyphs |
—
|
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: hieroglyphs | Statement: [Nepherites I, scriptUsedInMonuments, hieroglyphs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptUsedInMonuments Context triple: [Nepherites I, scriptUsedInMonuments, hieroglyphs]
-
A.
usedInMonument
Indicates that something serves as a material, component, or element incorporated into the construction or design of a monument.
-
B.
appliesToMonument
Indicates that something (such as a rule, status, or attribute) is relevant or applicable specifically to a monument.
-
C.
builtMonument
Indicates that one entity constructed or created a monument in honor of, or related to, another entity.
-
D.
monumentDepicts
Indicates that a monument visually represents, portrays, or is dedicated to a particular person, event, concept, or object.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f7296cd08190b5dde235602c4c01 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f49377411c8190b2188de444d76795 |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 21, 2026, 2:11 p.m.