Triple
T7523513
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mon people |
E177833
|
entity |
| Predicate | scriptInfluence |
P77309
|
FINISHED |
| Object | Burmese 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: Burmese script | Statement: [Mon people, scriptInfluence, Burmese script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptInfluence Context triple: [Mon people, scriptInfluence, Burmese script]
-
A.
scriptEvolution
Indicates how a script or written system changes, develops, or transforms over time in relation to its earlier or later forms.
-
B.
script
Indicates that an entity is associated with a written text or code (such as a screenplay, program, or written instructions) that defines its content or behavior.
-
C.
spinOffInfluence
Indicates that one entity has influenced the creation, direction, or characteristics of another entity that is derived from it as a spin-off.
-
D.
scriptDirection
Indicates the direction in which a writing system or script is read or written (e.g., left-to-right, right-to-left, top-to-bottom).
-
E.
scriptPromoted
Indicates that a script has been elevated in status or visibility, such as being featured, recommended, or moved to a higher-priority category.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c4f32081908b5162f4551adb6d |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f555455c81908850210bcad96ac2 |
completed | March 27, 2026, 9:23 p.m. |
Created at: March 27, 2026, 3:46 p.m.