Triple
T17377699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abcam |
E422482
|
entity |
| Predicate | hasResearchTool |
P24615
|
FINISHED |
| Object | Knockout-validated antibodies |
—
|
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: Knockout-validated antibodies | Statement: [Abcam, hasResearchTool, Knockout-validated antibodies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchTool Context triple: [Abcam, hasResearchTool, Knockout-validated antibodies]
-
A.
hasResearchFunction
Indicates that an entity possesses a role, capacity, or function specifically related to conducting or supporting research activities.
-
B.
hasResearchUse
chosen
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
C.
hasResearched
Indicates that an entity has conducted study, investigation, or systematic inquiry into another entity or topic.
-
D.
hasOnlineTools
Indicates that an entity provides or includes tools or functionalities that are accessible via the internet.
-
E.
hasResearcher
Indicates that an entity is associated with or linked to a specific researcher responsible for work, study, or investigation related to it.
- 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.