Triple
T29807290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Storm Corrosion |
E756871
|
entity |
| Predicate | hasCollaborationBetween |
P60681
|
FINISHED |
| Object | Steven Wilson |
—
|
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: Steven Wilson | Statement: [Storm Corrosion, hasCollaborationBetween, Steven Wilson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborationBetween Context triple: [Storm Corrosion, hasCollaborationBetween, Steven Wilson]
-
A.
containsCollaboration
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
B.
hasCollaboratedIn
chosen
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
C.
definesCollaborationBetween
Indicates that one entity specifies or establishes the terms or existence of a collaborative relationship between two or more entities.
-
D.
hasSiblingCollaboration
Indicates a collaborative relationship between two entities that are considered siblings within the same hierarchy or family.
-
E.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a00a74c0564819081e1c4c29b9d0d15 |
completed | May 10, 2026, 3:42 p.m. |
| PD | Predicate disambiguation | batch_6a00a6a63ef48190a743c88534d9d672 |
completed | May 10, 2026, 3:39 p.m. |
Created at: April 29, 2026, 5:21 p.m.