Triple
T22209516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngo Tuan Anh |
E548902
|
entity |
| Predicate | hasNotableSurnameBearerStatus |
P30307
|
FINISHED |
| Object | prominent bearer of the surname Ngo |
—
|
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: prominent bearer of the surname Ngo | Statement: [Ngo Tuan Anh, hasNotableSurnameBearerStatus, prominent bearer of the surname Ngo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableSurnameBearerStatus Context triple: [Ngo Tuan Anh, hasNotableSurnameBearerStatus, prominent bearer of the surname Ngo]
-
A.
hasNotableSurname
Indicates that an entity bears a surname that is recognized as notable, distinguished, or of particular significance.
-
B.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
C.
hasNotablePersonWithSurname
chosen
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
D.
hasBaseSurname
Indicates that an entity’s surname is derived from, or fundamentally corresponds to, a specified base or canonical surname.
-
E.
hasNotableBearerFamily
Indicates that a family is recognized for having at least one notable or distinguished member associated with it.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2aefb881909bddbabd4be0bd58 |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.