Triple
T28031656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami Sharks |
E708285
|
entity |
| Predicate | ownerInFilm |
P121203
|
FINISHED |
| Object | Christina Pagniacci |
—
|
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: Christina Pagniacci | Statement: [Miami Sharks, ownerInFilm, Christina Pagniacci]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerInFilm Context triple: [Miami Sharks, ownerInFilm, Christina Pagniacci]
-
A.
ownedByInFilm
chosen
Indicates that one entity is portrayed as being owned or possessed by another entity within the context of a specific film.
-
B.
directorOfWorkFeaturingSubject
Indicates that the subject is the director of a creative work in which another specified entity appears or is featured.
-
C.
directorAssociatedWith
Indicates a relationship where a director is professionally connected to, responsible for, or involved with a particular entity (such as a work, organization, or project).
-
D.
associatedWithProducerOfFilm
Indicates that one entity has an association or connection with the producer of a particular film.
-
E.
givenNameInFilm
Indicates that a person is referred to by a particular given (first) name within the context of a specific film.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:17 p.m.