Triple
T37322188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teyuna |
E926511
|
entity |
| Predicate | yearOfRediscovery |
P59308
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [Teyuna, yearOfRediscovery, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearOfRediscovery Context triple: [Teyuna, yearOfRediscovery, 1972]
-
A.
rediscoveryYear
chosen
Indicates the year in which something that was previously known but lost, forgotten, or overlooked was found or recognized again.
-
B.
rediscoveredIn
Indicates that something previously known but lost or forgotten was found or identified again at a particular time or place.
-
C.
rediscoveredAt
Indicates that an entity was found or identified again at a particular time or place after having been lost, forgotten, or unknown.
-
D.
rediscoveredInCentury
Indicates that something previously known but lost or forgotten was found or recognized again during a specified century.
-
E.
wasRediscoveredBy
Indicates that something previously known but lost, forgotten, or overlooked was found or identified again by a particular agent.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe779248c081909f0ed1a2a0df23db |
completed | May 8, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69fe76eaf6d48190998bc7168749cc42 |
completed | May 8, 2026, 11:51 p.m. |
Created at: May 3, 2026, 4:16 p.m.