Triple
T30348089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | noitaminA |
E771917
|
entity |
| Predicate | productionPartners |
P34923
|
FINISHED |
| Object | Fuji TV |
—
|
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: Fuji TV | Statement: [noitaminA, productionPartners, Fuji TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionPartners Context triple: [noitaminA, productionPartners, Fuji TV]
-
A.
partnerInProductionCompanyWith
Indicates that two entities are business partners together in operating or owning the same production company.
-
B.
formerManufacturerPartner
Indicates that two entities were previously in a manufacturer–partner business relationship, but that partnership has since ended.
-
C.
cooperationPartner
chosen
Indicates that two entities are engaged in a collaborative relationship, working together toward shared goals or mutual benefit.
-
D.
projectPartners
Indicates that two or more entities collaborate together as partners on the same project.
-
E.
primaryPartners
Indicates that the entities are each other’s main or most significant partners in a relationship, typically implying priority or exclusivity over other partnerships.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 29, 2026, 7:56 p.m.