Triple
T11204822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mangalia |
E265132
|
entity |
| Predicate | hasAncientHeritage |
P1494
|
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: [Mangalia, hasAncientHeritage, Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAncientHeritage Context triple: [Mangalia, hasAncientHeritage, Greek]
-
A.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
-
B.
hasAncientCityState
Indicates that one entity possesses, contains, or is associated with an ancient city-state as part of its historical or geographical context.
-
C.
associatedWithAncientEmpire
Indicates that one entity has a historical, cultural, political, or geographic connection or affiliation with an ancient empire.
-
D.
hasHeritage
chosen
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
E.
hasCulturalLegacyIn
Indicates that an entity has left a lasting cultural influence, impact, or heritage within a particular place, community, or cultural context.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d355c481908fc3d555b596314d |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.