Triple
T25353701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andréeneset |
E635760
|
entity |
| Predicate | discoveryOccurredIn |
P3986
|
FINISHED |
| Object | 1930 |
—
|
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: 1930 | Statement: [Andréeneset, discoveryOccurredIn, 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryOccurredIn Context triple: [Andréeneset, discoveryOccurredIn, 1930]
-
A.
wasDiscoveredAt
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
B.
discoveredSince
Indicates that one entity has been discovered starting from, or at some point after, a specified time or event associated with another entity.
-
C.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
D.
wasDiscoveredIn
chosen
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
E.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49dfedae88190a02f10196ef45ffa |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:34 p.m.