Triple
T38315941
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lana |
E1033824
|
entity |
| Predicate | scriptAlias |
P194053
|
FINISHED |
| Object | Lanna script |
—
|
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: Lanna script | Statement: [Lana, scriptAlias, Lanna script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptAlias Context triple: [Lana, scriptAlias, Lanna script]
-
A.
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.
-
B.
scriptAdapter
Indicates a relationship where one component adapts or translates a script or scripting interface so it can be used or executed within another system or context.
-
C.
scriptFileExtension
Indicates the file extension used for a script associated with an entity or system.
-
D.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
E.
scriptUser
Indicates that an entity functions as a user or executor of a particular script.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_69fd5d47da488190a4f2dbd44a0a83b2 |
completed | May 8, 2026, 3:49 a.m. |
Created at: May 3, 2026, 4:30 p.m.