Triple
T9022855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lerna |
E215768
|
entity |
| Predicate | languageOfAncientInhabitants |
P23482
|
FINISHED |
| Object | 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: Greek | Statement: [Lerna, languageOfAncientInhabitants, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfAncientInhabitants Context triple: [Lerna, languageOfAncientInhabitants, Greek]
-
A.
ancientLanguages
chosen
Indicates that the related entities are languages that originated in and were used during ancient historical periods.
-
B.
languageOfConquerors
Indicates that a language is associated with, used by, or imposed by a conquering group over the people or territory they have subjugated.
-
C.
associatedAncientPeoples
Indicates a relationship where certain ancient peoples are historically or culturally linked or connected to a given entity.
-
D.
ancientNameOf
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
E.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
- 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_69ca83a38aa88190bf1bb80c4548b5e2 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a454b808190af6bb48f7a4da917 |
completed | April 1, 2026, 12:43 a.m. |
| PD | Predicate disambiguation | batch_69cc5edf84408190aa5f57cb8bfd00e1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.