Triple
T36789012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cibinium |
E909000
|
entity |
| Predicate | hasModernRegionCapital |
P200159
|
FINISHED |
| Object | Sibiu |
—
|
NE NERFINISHED |
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: Sibiu | Statement: [Cibinium, hasModernRegionCapital, Sibiu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasModernRegionCapital Context triple: [Cibinium, hasModernRegionCapital, Sibiu]
-
A.
hasModernAdministrativeUnit
Indicates that an entity is associated with or belongs to a current, officially recognized administrative unit (such as a modern country, state, province, or municipality).
-
B.
hasModernTerritory
Indicates that an entity (typically a historical or former polity) corresponds geographically to the present-day territory of another entity (usually a modern state or region).
-
C.
containsModernCity
Indicates that one geographic or administrative region includes within its boundaries a currently existing modern city.
-
D.
hasModernNearbyCity
Indicates that an entity is located near or in proximity to a contemporary, currently existing city.
-
E.
regionCapitalSince
Indicates that one region has served as the capital of another region continuously since a specified point in time.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
| PDg | Predicate description generation | batch_69ff779d3d788190af5a2dbc4d7ca3c8 |
completed | May 9, 2026, 6:06 p.m. |
Created at: May 3, 2026, 4:12 p.m.