Triple
T27396269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-55 |
E691695
|
entity |
| Predicate | conductedExperimentsIn |
P31889
|
FINISHED |
| Object | materials science |
—
|
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: materials science | Statement: [STS-55, conductedExperimentsIn, materials science]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conductedExperimentsIn Context triple: [STS-55, conductedExperimentsIn, materials science]
-
A.
experimentedOn
chosen
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
B.
experimentedOnBy
Indicates that an entity has been the subject or object of an experiment conducted by another entity.
-
C.
conductedResearchOn
Indicates that an entity has performed or carried out research concerning another entity or topic.
-
D.
medicalExperimentsConductedBy
Indicates that medical experiments are performed, overseen, or carried out by a specified agent or organization.
-
E.
notableExperiment
Indicates that an entity is recognized for having conducted or been the subject of a particularly important or influential experiment.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cd2ceb481908cd9fae52a542206 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 12:27 p.m.