Triple
T3112875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lao |
E64990
|
entity |
| Predicate | primaryWritingDirection |
P2264
|
FINISHED |
| Object | left-to-right |
—
|
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: left-to-right | Statement: [Lao, primaryWritingDirection, left-to-right]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWritingDirection Context triple: [Lao, primaryWritingDirection, left-to-right]
-
A.
hasWritingDirection
chosen
Indicates the direction in which writing or text is read or written for a given script, language, or text system.
-
B.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
C.
translationDirection
Indicates the source and target languages involved in a translation, specifying the direction from the original language to the translated language.
-
D.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
E.
languageOfWritings
Indicates that a specified language is the one in which certain writings or written works are composed.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43c79448190aa72f707319e8c5e |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.