Triple
T8477455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phigalia |
E200430
|
entity |
| Predicate | languageSpokenInAntiquity |
P1434
|
FINISHED |
| Object | Ancient Greek |
—
|
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: Ancient Greek | Statement: [Phigalia, languageSpokenInAntiquity, Ancient Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageSpokenInAntiquity Context triple: [Phigalia, languageSpokenInAntiquity, Ancient Greek]
-
A.
ancientLanguages
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
B.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
-
C.
historicallySpokenIn
chosen
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
D.
languageOfConquerors
Indicates that a language is associated with, used by, or imposed by a conquering group over the people or territory they have subjugated.
-
E.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe51ffab881908448aff899511f2c |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.