Triple
T16319250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Định Tường Province |
E396247
|
entity |
| Predicate | presentTerritoryIncludes |
P11790
|
FINISHED |
| Object | Tiền Giang Province |
—
|
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: Tiền Giang Province | Statement: [Định Tường Province, presentTerritoryIncludes, Tiền Giang Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: presentTerritoryIncludes Context triple: [Định Tường Province, presentTerritoryIncludes, Tiền Giang Province]
-
A.
territoryIncluded
chosen
Indicates that one territory is geographically or administratively contained within another territory.
-
B.
sometimesIncludesTerritory
Indicates that one entity occasionally, but not consistently, encompasses or contains the territory of another entity.
-
C.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
-
D.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
E.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b4ad448190b2b195a5e0032c6e |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.