Triple
T31349313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wide Prairie |
E799542
|
entity |
| Predicate | includesCollaborationsWith |
P38701
|
FINISHED |
| Object | Paul McCartney |
—
|
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: Paul McCartney | Statement: [Wide Prairie, includesCollaborationsWith, Paul McCartney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesCollaborationsWith Context triple: [Wide Prairie, includesCollaborationsWith, Paul McCartney]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
hasCollaborationsWithinCircle
Indicates that an entity engages in collaborative relationships with other entities that belong to the same defined group or circle.
-
C.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
D.
hasNotableCollaborationType
Indicates a specific kind or category of significant collaborative relationship that exists between entities.
-
E.
collaborationOf
chosen
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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a011ee3507081908b42de4278ae0b83 |
completed | May 11, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_6a011e874420819091cac3f08e8aa3f9 |
completed | May 11, 2026, 12:10 a.m. |
Created at: April 29, 2026, 9:17 p.m.