Triple
T13733105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spymob |
E329860
|
entity |
| Predicate | roleInCollaboration |
P45538
|
FINISHED |
| Object | backing band for N*E*R*D |
—
|
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: backing band for N*E*R*D | Statement: [Spymob, roleInCollaboration, backing band for N*E*R*D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCollaboration Context triple: [Spymob, roleInCollaboration, backing band for N*E*R*D]
-
A.
collaboratorRole
chosen
Indicates the specific function, position, or capacity in which one collaborator participates in a shared activity or project with another.
-
B.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
C.
roleInIntegration
Indicates the specific function or responsibility an entity has within a combined or coordinated system, process, or integration.
-
D.
roleInvolves
Indicates that a particular role includes or requires participation in a specified activity, responsibility, or function.
-
E.
roleInOperation
Indicates that an entity holds a specific function, duty, or position within a particular operation or 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_69d80772315881908f980cae40d91664 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69de0201d3c48190aa306be231a28bc1 |
completed | April 14, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69dbbe950b148190ba0df8a749269ec6 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:55 p.m.