Triple
T33762037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitsis/Horowitz |
E865133
|
entity |
| Predicate | knownForCollaborationBetween |
P8554
|
FINISHED |
| Object | Edward Kitsis |
—
|
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: Edward Kitsis | Statement: [Kitsis/Horowitz, knownForCollaborationBetween, Edward Kitsis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCollaborationBetween Context triple: [Kitsis/Horowitz, knownForCollaborationBetween, Edward Kitsis]
-
A.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
B.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
notableCollaboration
chosen
Indicates a significant joint effort or partnership between entities that produced a noteworthy shared outcome or work.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
knownForFeaturing
Indicates that one entity is notable or recognized for prominently including, presenting, or showcasing 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_69f3498d3b748190aa3c4006c1f32f38 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 1:45 a.m.