Triple
T5982174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ho Chi Minh Order |
E133144
|
entity |
| Predicate | hasRankInSystem |
P47925
|
FINISHED |
| Object | second-highest order of Vietnam |
—
|
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: second-highest order of Vietnam | Statement: [Ho Chi Minh Order, hasRankInSystem, second-highest order of Vietnam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankInSystem Context triple: [Ho Chi Minh Order, hasRankInSystem, second-highest order of Vietnam]
-
A.
hasRankCategory
Indicates that an entity is assigned to a particular rank-based classification or level within an ordered hierarchy.
-
B.
isRank
chosen
Indicates that one entity serves as the rank, level, or hierarchical position associated with another entity.
-
C.
hasRankContext
Indicates that an entity’s rank or ordering is defined, interpreted, or constrained within a specific contextual framework or situation.
-
D.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
E.
hasLegalRank
Indicates that an entity holds a specific legal status, classification, or rank within a formal legal or regulatory system.
- 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_69c0086f45e8819098f73dd16d45ec9d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6921b081908a6f6323d5c7a062 |
completed | March 22, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:04 p.m.