Triple
T13428467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tai Lue language |
E313543
|
entity |
| Predicate | scriptStandardized |
P7508
|
FINISHED |
| Object | New Tai Lue script in 1950s |
—
|
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: New Tai Lue script in 1950s | Statement: [Tai Lue language, scriptStandardized, New Tai Lue script in 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptStandardized Context triple: [Tai Lue language, scriptStandardized, New Tai Lue script in 1950s]
-
A.
scriptStandardizationCenter
Indicates a relationship where an entity serves as a center or authority responsible for standardizing a writing system or script.
-
B.
scriptUsedForStandardization
Indicates that a particular writing system or script is employed as the standard reference form for normalizing or harmonizing text or data.
-
C.
documentationStandard
Indicates that there is a specified convention or set of rules governing how documentation should be written, structured, or maintained in relation to an entity or process.
-
D.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
-
E.
standardizedIn
chosen
Indicates that something has been formally defined, regulated, or made uniform within a particular standard, framework, or jurisdiction.
- 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_69d806ad0c44819088833ae1ec9e9690 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaed1f9208190bf5ef5b8a7ded376 |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03926188190ab3948d1f5d3941f |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:40 p.m.