Triple
T28206183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PoP! |
E717028
|
entity |
| Predicate | frontedByActor |
P30063
|
FINISHED |
| Object | Hugh Grant |
—
|
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: Hugh Grant | Statement: [PoP!, frontedByActor, Hugh Grant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontedByActor Context triple: [PoP!, frontedByActor, Hugh Grant]
-
A.
frontedByFictionalCharacter
Indicates that something (such as a show, series, or franchise) is led, hosted, or prominently represented by a fictional character.
-
B.
frontedByPortrayedBy
Indicates that the front-facing representation of an entity (such as a work, object, or concept) is provided or embodied by a particular portraying entity (such as a person, image, or character).
-
C.
facedBy
Indicates that one entity is oriented toward and directly opposite another entity, such that it is facing it.
-
D.
commonlyFrontedBy
Indicates that one element is typically placed at the beginning or in the leading position of another element.
-
E.
primaryActor
chosen
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
- 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_69efd6b826908190857e6e7dad74ed93 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 27, 2026, 10:35 p.m.