Triple
T9976173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giap |
E196333
|
entity |
| Predicate | belongsToOnomasticsCategory |
P22351
|
FINISHED |
| Object | Vietnamese masculine given names |
—
|
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: Vietnamese masculine given names | Statement: [Giap, belongsToOnomasticsCategory, Vietnamese masculine given names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToOnomasticsCategory Context triple: [Giap, belongsToOnomasticsCategory, Vietnamese masculine given names]
-
A.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
B.
hasOnomasticField
chosen
Indicates a relationship where something is associated with a specific onomastic field, i.e., a domain or category related to names or naming conventions.
-
C.
belongsToNamingTradition
Indicates that an entity is associated with or classified under a particular naming tradition or convention.
-
D.
belongsToCatalogOf
Indicates that one item is included within, or is a member of, a particular catalog or collection.
-
E.
canBelongTo
Indicates that something is capable of being a member or part of a particular group, category, or owner.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84b47308190aa2f94fa7320cdc3 |
completed | April 2, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.