Triple
T23189764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dionne & Friends |
E579697
|
entity |
| Predicate | isOneTimeCollaboration |
P128774
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Dionne & Friends, isOneTimeCollaboration, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOneTimeCollaboration Context triple: [Dionne & Friends, isOneTimeCollaboration, true]
-
A.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
B.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
D.
isOneOffProject
chosen
Indicates that the project is a unique, non-recurring effort rather than part of an ongoing or repeated series of projects.
-
E.
usesCollaboration
Indicates that one entity employs or relies on collaborative methods, tools, or partnerships with another entity to achieve a shared goal or perform an activity.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd65e008190a724619a107d7bd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.