Triple
T3462607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sebaste |
E73060
|
entity |
| Predicate | majorUrbanCenterIn |
P48921
|
FINISHED |
| Object | Hellenistic period |
—
|
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: Hellenistic period | Statement: [Sebaste, majorUrbanCenterIn, Hellenistic period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorUrbanCenterIn Context triple: [Sebaste, majorUrbanCenterIn, Hellenistic period]
-
A.
majorPopulationCenter
Indicates that a location functions as a primary hub of population concentration and activity within a region.
-
B.
capitalOrMajorCenter
Indicates that a location serves as a capital city or a primary major center (political, economic, or cultural hub) for a larger region or entity.
-
C.
otherMajorCity
Indicates that one city is another major city associated with or comparable in importance or status to the first city.
-
D.
largestUrbanConcentrationIn
Indicates that an entity represents the biggest or most populous urban area located within a specified geographic region.
-
E.
majorCityOnSystem
Indicates that a city serves as a primary or significant urban center located on or within a particular system (such as a transportation, planetary, or infrastructural system).
- F. None of above. chosen
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_69ad85b224d481908ff8be51338d24ff |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adbae867c4819091c76e63e44290b4 |
completed | March 8, 2026, 6:07 p.m. |
| PD | Predicate disambiguation | batch_69adae05bb0081909dc7e4779d6e05ef |
completed | March 8, 2026, 5:12 p.m. |
| PDg | Predicate description generation | batch_69adb1ecb02881908394f197e31431b4 |
completed | March 8, 2026, 5:29 p.m. |
Created at: March 8, 2026, 3:17 p.m.