Triple
T17377849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambridge Antibody Technology |
E422486
|
entity |
| Predicate | developedTechnologyUsedIn |
P41521
|
FINISHED |
| Object | adalimumab |
—
|
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: adalimumab | Statement: [Cambridge Antibody Technology, developedTechnologyUsedIn, adalimumab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedTechnologyUsedIn Context triple: [Cambridge Antibody Technology, developedTechnologyUsedIn, adalimumab]
-
A.
technologyUsedIn
chosen
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
B.
inUniverseTechnologyDeveloped
Indicates that a specific technology has been created or developed within the context of a particular fictional or defined universe.
-
C.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
D.
developsTechnologyFor
Indicates that one entity creates, improves, or engineers technology specifically intended to be used by or to benefit another entity.
-
E.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
- 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_69d889d6535c81908be333c01deaec4e |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a6ea56c8190b56d966ccf2c91f7 |
completed | April 19, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_69e3b02ac8688190a7182f1b2151d721 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:45 a.m.