Triple
T10052133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BioFrontiers Institute |
E207771
|
entity |
| Predicate | collaborativeModel |
P1854
|
FINISHED |
| Object | cross-disciplinary teams |
—
|
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: cross-disciplinary teams | Statement: [BioFrontiers Institute, collaborativeModel, cross-disciplinary teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborativeModel Context triple: [BioFrontiers Institute, collaborativeModel, cross-disciplinary teams]
-
A.
collaborationModel
chosen
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
B.
collaborativeWork
Indicates a relationship where two or more entities jointly contribute effort or resources toward a shared task, project, or goal.
-
C.
isCollaborative
Indicates that two or more entities work together jointly toward a shared goal or outcome.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
collaborationAspect
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf9135bc8190a48a2e5cbafca0cd |
completed | April 2, 2026, 2:08 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8d2280819089de27e57babd1f3 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:56 p.m.