Triple
T26552892
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inscriptions of Petén |
E671725
|
entity |
| Predicate | scriptTypeDescribed |
P4427
|
FINISHED |
| Object | logosyllabic writing system |
—
|
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: logosyllabic writing system | Statement: [Inscriptions of Petén, scriptTypeDescribed, logosyllabic writing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptTypeDescribed Context triple: [Inscriptions of Petén, scriptTypeDescribed, logosyllabic writing system]
-
A.
scriptType
chosen
Indicates the classification or category of a script, specifying what kind of script it is (e.g., its format, purpose, or scripting language type).
-
B.
scriptTypeWorkedOn
Indicates the type or category of script that an entity has worked on or contributed to.
-
C.
scriptCategory
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
-
D.
scriptNameLanguage
Indicates that a script’s name is expressed or written in a particular language.
-
E.
scriptOfReferent
Indicates that a script (e.g., writing system or code) is associated with, or used to represent, a particular referent.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 1:48 a.m.