Triple
T4441166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Junior |
E95772
|
entity |
| Predicate | featuresExperiment |
P56522
|
FINISHED |
| Object | experimental fertility drug |
—
|
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: experimental fertility drug | Statement: [Junior, featuresExperiment, experimental fertility drug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresExperiment Context triple: [Junior, featuresExperiment, experimental fertility drug]
-
A.
includesExperiment
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
-
B.
supportsExperiment
Indicates that one entity provides the necessary resources, conditions, or assistance for an experiment to be conducted or to function as intended.
-
C.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
D.
featuresSetting
Indicates that something includes, presents, or highlights a particular setting as a notable or primary aspect.
-
E.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355ad71588190b1dcad4250472c29 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:32 p.m.