Triple
T7731163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael P. Shawver |
E175257
|
entity |
| Predicate | collaborationFrequencyWithRyanCoogler |
P78406
|
FINISHED |
| Object | frequent |
—
|
LITERAL FINISHED |
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: frequent | Statement: [Michael P. Shawver, collaborationFrequencyWithRyanCoogler, frequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationFrequencyWithRyanCoogler Context triple: [Michael P. Shawver, collaborationFrequencyWithRyanCoogler, frequent]
-
A.
workedWithDirector
Indicates that one entity has collaborated professionally with a director on a project or production.
-
B.
coDirectedWith
Indicates that two or more entities jointly directed the same work or project.
-
C.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
D.
collaborationAt
Indicates that two or more entities are working together or jointly engaged in an activity, project, or context at a specific place, organization, or event.
-
E.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
- F. None of above. chosen
Provenance (4 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_69c6995e912c81909a49a2657103f786 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
| PDg | Predicate description generation | batch_69c7040091608190a9e46ecfb2ff0bca |
completed | March 27, 2026, 10:26 p.m. |
Created at: March 27, 2026, 4:06 p.m.