Triple
T38315946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lana |
E1033824
|
entity |
| Predicate | codeScriptCategory |
P11938
|
FINISHED |
| Object | historic script |
—
|
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: historic script | Statement: [Lana, codeScriptCategory, historic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeScriptCategory Context triple: [Lana, codeScriptCategory, historic script]
-
A.
scriptCategory
chosen
Indicates the classification or type of script to which an entity (such as a written work, code, or performance text) belongs.
-
B.
scriptCode
Indicates that an entity is associated with a particular writing system or script, identified by a standardized script code.
-
C.
codeNameCategory
Indicates that an entity’s code name belongs to or is classified under a particular category of code names.
-
D.
codeSpace
Indicates the namespace or contextual scope within which a piece of code, identifier, or programming element is defined and interpreted.
-
E.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.