Triple
T23439665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HitRecord |
E565359
|
entity |
| Predicate | hasNotableLeaderOccupation |
P13522
|
FINISHED |
| Object | actor |
—
|
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: actor | Statement: [HitRecord, hasNotableLeaderOccupation, actor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLeaderOccupation Context triple: [HitRecord, hasNotableLeaderOccupation, actor]
-
A.
notableHolderOccupation
Indicates that a person notably associated with an entity (e.g., an award, office, or title) held a particular occupation or professional role.
-
B.
hasNotablePoliticalRoleIn
Indicates that an entity holds or has held a significant political position, function, or influence within a specified context or jurisdiction.
-
C.
hasNotableBearerOccupation
chosen
Indicates that an entity is associated with a notable person who holds a specific occupation.
-
D.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
E.
notableLeaderAlias
Indicates that an alternative or commonly used name (alias) is associated with a notable leader.
- 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_69e24584f9488190bb32730bd2ce023e |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f1a5de713c8190b35bfa66dddbd5af |
completed | April 29, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:50 p.m.