Triple
T15002769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Severus and Celer |
E374131
|
entity |
| Predicate | collaboratedWithEachOther |
P38701
|
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: [Severus and Celer, collaboratedWithEachOther, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratedWithEachOther Context triple: [Severus and Celer, collaboratedWithEachOther, true]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
collaborationOf
chosen
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
collaboratedWithInKeyWork
Indicates that two or more entities worked together in creating or contributing to a specific, significant work or project.
-
D.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership with another entity.
-
E.
establishedInCollaborationWith
Indicates that something was created, founded, or set up jointly through cooperative effort between two or more parties.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7312ae48190bdaf91ecced6657e |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.