Triple
T29013746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Think! (short story) |
E737242
|
entity |
| Predicate | hasMainExperiment |
P37454
|
FINISHED |
| Object | mind-reading experiment |
—
|
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: mind-reading experiment | Statement: [Think! (short story), hasMainExperiment, mind-reading experiment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainExperiment Context triple: [Think! (short story), hasMainExperiment, mind-reading experiment]
-
A.
hasTypeOfExperiment
Indicates that an experiment is associated with or classified under a specific type or category of experiment.
-
B.
majorExperiment
Indicates that an entity conducts or is involved in a primary, large-scale, or most significant experiment in a given context.
-
C.
experimentedOn
Indicates that one entity conducted experiments or tests on another entity as the subject of investigation.
-
D.
includesExperiment
chosen
Indicates that one entity contains or encompasses a specific experiment as part of its scope, composition, or content.
-
E.
showedInExperiments
Indicates that something was demonstrated or observed to occur within the context of experiments.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: April 28, 2026, 9:44 a.m.