Triple
T4233183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gia Định Province |
E94628
|
entity |
| Predicate | scriptOfHistoricalName |
P4037
|
FINISHED |
| Object | chữ Nôm |
—
|
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: chữ Nôm | Statement: [Gia Định Province, scriptOfHistoricalName, chữ Nôm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptOfHistoricalName Context triple: [Gia Định Province, scriptOfHistoricalName, chữ Nôm]
-
A.
historicalScript
chosen
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
B.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
C.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
-
D.
historicalFigure
Indicates that an entity is recognized as a notable person from the past who played a significant role in history.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e65720c819087c4022c774ff7c3 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f3bd188190b0cd613e8a5c1683 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:05 p.m.