Triple
T10362775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Catalan choir |
E244176
|
entity |
| Predicate | isTypicallyBasedIn |
P93876
|
FINISHED |
| Object | countries with Catalan diaspora communities |
—
|
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: countries with Catalan diaspora communities | Statement: [Catalan choir, isTypicallyBasedIn, countries with Catalan diaspora communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTypicallyBasedIn Context triple: [Catalan choir, isTypicallyBasedIn, countries with Catalan diaspora communities]
-
A.
hasBaseOfOperations
Indicates that an entity uses a particular location as its primary place of operation or activity.
-
B.
basedInCity
Indicates that an entity has its primary location, headquarters, or main operations situated in a specified city.
-
C.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
-
D.
hasPublisherHeadquartersIn
Indicates that the main corporate headquarters of a publishing entity is located in a specified place.
-
E.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e962f08c8190a7ac489dc524510d |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, noon