Triple
T35801750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altar of Zeus in Pergamon |
E1034995
|
entity |
| Predicate | locatedInPresentRegion |
P96807
|
FINISHED |
| Object | Bergama |
E315646
|
NE 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: Bergama | Statement: [Altar of Zeus in Pergamon, locatedInPresentRegion, Bergama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInPresentRegion Context triple: [Altar of Zeus in Pergamon, locatedInPresentRegion, Bergama]
-
A.
locatedInCurrentCountry
Indicates that an entity is situated within the geographic boundaries of the country in which it is presently found.
-
B.
locatedInStateOrRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specified state or region.
-
C.
meetsCurrentRegion
Indicates that an entity’s location or state aligns with, or falls within, the currently defined region.
-
D.
locatedInUSRegion
Indicates that one entity is geographically situated within a specified region of the United States.
-
E.
locatedNearRegion
Indicates that one entity is situated in close geographic proximity to a specified region.
- F. None of above.
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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38bfc2c3b481909473399d3de9e569 |
completed | June 22, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.