Triple
T21485324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federalism |
E530101
|
entity |
| Predicate | concurrentCompetenceArea |
P144537
|
FINISHED |
| Object | taxation |
—
|
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: taxation | Statement: [German federalism, concurrentCompetenceArea, taxation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrentCompetenceArea Context triple: [German federalism, concurrentCompetenceArea, taxation]
-
A.
competenceArea
Indicates that one entity has a particular domain, field, or area in which it possesses competence, expertise, or responsibility.
-
B.
definesCompetenceOf
Indicates that one entity specifies, determines, or establishes the scope, level, or nature of another entity’s competence or capability.
-
C.
sharesCompetencesWith
Indicates that two entities possess and can apply the same or overlapping set of skills, abilities, or areas of expertise.
-
D.
competence
Indicates that an entity has the ability, skill, or qualification to perform a task or fulfill a role effectively.
-
E.
regulatesCompetenceIn
Indicates that one entity controls, influences, or modulates the ability or readiness of another entity to perform a specific function or process.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea365a8481909635f614b23e751f |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:21 p.m.