Triple
T28180569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 浏阳 |
E716014
|
entity |
| Predicate | hasFamousPerson |
P97477
|
FINISHED |
| Object | 胡耀邦 |
—
|
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: 胡耀邦 | Statement: [浏阳, hasFamousPerson, 胡耀邦]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamousPerson Context triple: [浏阳, hasFamousPerson, 胡耀邦]
-
A.
hasNotablePersonWithGivenName
Indicates that there exists a notable person associated with the subject whose given (first) name matches the specified value.
-
B.
hasFamousNamesake
Indicates that an entity shares its name with another well-known or notable entity.
-
C.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
D.
famousIndividual
Indicates that an individual is widely known and recognized by a large number of people, typically for notable achievements, status, or public visibility.
-
E.
hasNotablePeople
chosen
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 27, 2026, 10:19 p.m.