Triple
T31045852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Segorbe |
E791123
|
entity |
| Predicate | hasDemographicUnit |
P196087
|
FINISHED |
| Object | Segorbinos |
—
|
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: Segorbinos | Statement: [Segorbe, hasDemographicUnit, Segorbinos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDemographicUnit Context triple: [Segorbe, hasDemographicUnit, Segorbinos]
-
A.
hasDemographic
Indicates that an entity is associated with or characterized by a particular demographic group or attribute.
-
B.
hasDemographicPresenceIn
Indicates that a particular demographic group exists or is represented within a specified geographic area or population context.
-
C.
hasDemographicPattern
Indicates that there is a characteristic distribution or trend of attributes (such as age, gender, income, or ethnicity) within a population or group.
-
D.
hasDemographicCenter
Indicates that an entity has a primary geographic location where the majority or core concentration of its associated population or demographic group is found.
-
E.
hasDemographicsCountry
Indicates that an entity’s demographic information is associated with or pertains to a specific country.
- 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 29, 2026, 8:59 p.m.