Triple
T30487519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yoso |
E775760
|
entity |
| Predicate | notableMemberFrom |
P207277
|
FINISHED |
| Object | Yes |
—
|
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: Yes | Statement: [Yoso, notableMemberFrom, Yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMemberFrom Context triple: [Yoso, notableMemberFrom, Yes]
-
A.
notableMemberWorld
Indicates that an entity is a particularly prominent or distinguished member within a global or worldwide group, organization, or context.
-
B.
notableMemberVariant
Indicates that an entity is a specific variant or version of a notable member within a group, class, or category.
-
C.
notableMemberNationality
Indicates that the notable member of a group or organization has the specified nationality.
-
D.
notableIndividuals
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
E.
notableMemberBecame
Indicates that an individual who is a notable member of one group, organization, or category transitioned into or assumed a role, status, or membership in another.
- F. None of above. chosen
Provenance (4 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_69f22497f91c8190afa7165bc900accd |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 8:13 p.m.