Triple
T33502988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalanism |
E858044
|
entity |
| Predicate | keyTerritory |
P96827
|
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: [Catalanism, keyTerritory, Catalonia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyTerritory Context triple: [Catalanism, keyTerritory, Catalonia]
-
A.
territoryType
Indicates the specific kind or classification of a territory associated with an entity (e.g., country, region, zone, or jurisdiction type).
-
B.
definedTerritoryOf
Indicates that one entity specifies or establishes the official territorial boundaries or jurisdiction of another entity.
-
C.
territoryCorrespondedTo
Indicates that one territory matched, aligned with, or was equivalent to another territory in scope, boundaries, or designation.
-
D.
refersToTerritory
chosen
Indicates that one entity designates, mentions, or is associated with a specific geographic area or territorial domain.
-
E.
recognizedTerritory
Indicates that one entity formally acknowledges another entity’s claim of authority or ownership over a specific geographic area.
- 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_69f3497660508190a541826a81f7e9ab |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e59cb7ac81909531fb256dadb474 |
completed | May 3, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.