Triple
T31633776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria waterlily |
E807240
|
entity |
| Predicate | discoveredInScience |
P3986
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Victoria waterlily, discoveredInScience, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveredInScience Context triple: [Victoria waterlily, discoveredInScience, 19th century]
-
A.
subjectOfDiscovery
Indicates that an entity is the topic, object, or focus that has been discovered in a discovery event or process.
-
B.
wasDiscoveredIn
chosen
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
C.
madeDiscoveryOn
Indicates that an entity discovered or identified something on a specific date or at a specific point in time.
-
D.
inspiredDiscoveryOf
Indicates that one entity’s ideas, actions, or work motivated or led directly to another entity’s discovery.
-
E.
discoveriesInclude
Indicates that one entity’s set of discoveries contains or encompasses the other entity as a discovered item.
- 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_69f348d892948190915f8facacb9568c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 30, 2026, 10:46 p.m.