Triple
T28165055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laietania |
E715002
|
entity |
| Predicate | modernRegionTerritory |
P25757
|
FINISHED |
| Object | Catalonia |
—
|
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: Catalonia | Statement: [Laietania, modernRegionTerritory, Catalonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernRegionTerritory Context triple: [Laietania, modernRegionTerritory, Catalonia]
-
A.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
B.
modernTerritoryIncludes
Indicates that the geographic area of one modern political or administrative territory fully or partially contains the geographic area of another.
-
C.
modernRegion
chosen
Indicates that an entity is located within or associated with a contemporary, present-day geographic or administrative region.
-
D.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
E.
governedTerritory
Indicates that one entity exercises political authority or control over another entity or geographic area as its governing power.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 10:09 p.m.