Triple
T35805070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PG Era |
E1035082
|
entity |
| Predicate | prominentStarsInclude |
P5563
|
FINISHED |
| Object | John Cena |
—
|
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: John Cena | Statement: [PG Era, prominentStarsInclude, John Cena]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prominentStarsInclude Context triple: [PG Era, prominentStarsInclude, John Cena]
-
A.
notableStar
Indicates that the subject is a star (or stellar object) that is distinguished or noteworthy in some significant way, such as brightness, fame, or scientific interest, relative to other stars.
-
B.
starredActor
chosen
Indicates that an actor performed a leading or significant role in a particular production or work.
-
C.
notableStarName
Indicates that the subject is known by the specified star name as a notable or prominent designation.
-
D.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
-
E.
notableWorkStar
Indicates that a particular work (such as a film, show, or production) is one of the notable works in which the specified star (person) prominently appears or performs.
- 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.