Triple
T808455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protectorate of Annam |
E17488
|
entity |
| Predicate | latinScript |
P454
|
FINISHED |
| Object | quốc ngữ |
—
|
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: quốc ngữ | Statement: [Protectorate of Annam, latinScript, quốc ngữ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: latinScript Context triple: [Protectorate of Annam, latinScript, quốc ngữ]
-
A.
writingSystem
chosen
Indicates that one entity is the script or system of written symbols used to represent the language or content of another entity.
-
B.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
C.
languageFamilyWritten
Indicates that one language family is represented or recorded in a particular written form or script.
-
D.
usesAdditionalLettersFrom
Indicates that one entity forms or derives its representation by incorporating extra letters taken from another entity beyond those originally present.
-
E.
alternativeTransliteration
Indicates that one written form represents an alternative way of transliterating the same original text or name into another script or orthography.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.