Triple
T26962830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bengalese finch |
E679090
|
entity |
| Predicate | researchAdvantage |
P164303
|
FINISHED |
| Object | tolerant of handling |
—
|
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: tolerant of handling | Statement: [Bengalese finch, researchAdvantage, tolerant of handling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchAdvantage Context triple: [Bengalese finch, researchAdvantage, tolerant of handling]
-
A.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
B.
researchAccess
Indicates that one entity is permitted to access, use, or retrieve another entity specifically for research-related purposes.
-
C.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
D.
researchStrength
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
E.
researchComponent
Indicates that an entity functions as a part or element within a broader research activity, project, or study.
- F. None of above. chosen
Provenance (4 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_69eeeb4f3a448190b1e94b2d4776c16e |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f644de4a84819087ddb84757fc4585 |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f643e818d481908fc66bc91bd25d77 |
completed | May 2, 2026, 6:35 p.m. |
Created at: April 27, 2026, 6:33 a.m.