Triple
T34202465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Metropolitan Archbishop |
E877423
|
entity |
| Predicate | greekRootOfMetropolitan |
P178234
|
FINISHED |
| Object | metropolis (mother city) |
—
|
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: metropolis (mother city) | Statement: [Metropolitan Archbishop, greekRootOfMetropolitan, metropolis (mother city)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: greekRootOfMetropolitan Context triple: [Metropolitan Archbishop, greekRootOfMetropolitan, metropolis (mother city)]
-
A.
recognizedAsGreekBy
Indicates that one entity is regarded or acknowledged as Greek by another entity.
-
B.
hasNameInGreek
Indicates that an entity is associated with a specific representation of its name in the Greek language.
-
C.
oneOfMajorGreekEthne
Indicates that an entity belongs to one of the primary traditional Greek ethnic groups (ethne).
-
D.
majorGreekEthnosAlongside
Indicates that one ethnic group is recognized as a major Greek ethnos existing alongside another, at a comparable level of prominence or status.
-
E.
keyGreekTerm
chosen
Indicates that an entity is identified as the primary or canonical Greek term associated with another entity or concept.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7104bcc1c8190b99eed0d5b1faf90 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.