Triple
T30211399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Τεγέα |
E768074
|
entity |
| Predicate | hasFindsDisplayedAt |
P195772
|
FINISHED |
| Object | Archaeological Museum of Tegea |
—
|
NE NERFINISHED |
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: Archaeological Museum of Tegea | Statement: [Τεγέα, hasFindsDisplayedAt, Archaeological Museum of Tegea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFindsDisplayedAt Context triple: [Τεγέα, hasFindsDisplayedAt, Archaeological Museum of Tegea]
-
A.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
B.
foundAs
Indicates that one entity is discovered, identified, or observed in the role, form, or state represented by another entity.
-
C.
ashFoundIn
Indicates that ash is present within, or has been discovered in, a specified location or material.
-
D.
hasFindingSite
Indicates that a particular finding, observation, or abnormality is located in or associated with a specific anatomical site.
-
E.
foundToBe
Indicates that something has been determined or discovered, often through investigation or evaluation, to possess a particular quality, status, or condition.
- F. None of above. chosen
Provenance (4 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fde5d7d9548190880a9d95b8f0f66b |
completed | May 8, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69fde4e1bf9c81909754545275eccc03 |
completed | May 8, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69fde5d677b88190bc904e6df8617c18 |
completed | May 8, 2026, 1:32 p.m. |
Created at: April 29, 2026, 7:32 p.m.