Triple
T37356896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German federal institutions |
E927477
|
entity |
| Predicate | excludeLevel |
P34541
|
FINISHED |
| Object | state level (Länder) |
—
|
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: state level (Länder) | Statement: [German federal institutions, excludeLevel, state level (Länder)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: excludeLevel Context triple: [German federal institutions, excludeLevel, state level (Länder)]
-
A.
exportLevel
Indicates the degree or extent to which something is produced in one place and sent out or made available to other places or markets.
-
B.
excludedFrom
chosen
Indicates that one entity is deliberately not included within the scope, membership, or applicability of another entity or set.
-
C.
coversLevel
Indicates that one entity includes or encompasses a particular level or layer of another entity or system.
-
D.
restrictionLevel
Indicates the degree or strictness of limitations or constraints imposed on an entity, action, or access.
-
E.
excludes
Indicates that one entity deliberately omits, leaves out, or does not allow the inclusion of another entity within a set, group, or context.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.