Triple
T24766262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pac-Man |
E619590
|
entity |
| Predicate | appliedDuringCareerOf |
P96605
|
FINISHED |
| Object | Manny Pacquiao |
—
|
NE NERFINISHED |
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: Manny Pacquiao | Statement: [Pac-Man, appliedDuringCareerOf, Manny Pacquiao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedDuringCareerOf Context triple: [Pac-Man, appliedDuringCareerOf, Manny Pacquiao]
-
A.
spentEntireCareerWith
Indicates that an individual has worked exclusively for a single organization or team for the full duration of their professional career.
-
B.
laterCareerWorkOf
Indicates that one work represents a creator’s later career output in relation to another work or to their overall body of work.
-
C.
associatedWithCareerOf
chosen
Indicates a relationship where something is connected or relevant to a person’s professional life, occupation, or career trajectory.
-
D.
workedAs
Indicates that an entity held a particular job, role, or position, performing work in that capacity.
-
E.
managedCareerOf
Indicates that one entity was responsible for overseeing, directing, or handling the professional career of another entity.
- 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_69e2fabbea94819092ed41348909622f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 4:28 a.m.