Triple
T6363519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Council (Germany) |
E143169
|
entity |
| Predicate | numberOfRepresentedSubdivisions |
P1905
|
FINISHED |
| Object | 16 |
—
|
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: 16 | Statement: [Federal Council (Germany), numberOfRepresentedSubdivisions, 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfRepresentedSubdivisions Context triple: [Federal Council (Germany), numberOfRepresentedSubdivisions, 16]
-
A.
subdividedBy
Indicates that something is divided into smaller parts or sections by another entity or criterion.
-
B.
isSubdividedFrom
Indicates that one entity represents a subdivision or derived part that has been split off from another entity.
-
C.
hasNumberOfDivisions
chosen
Indicates the relationship that specifies how many divisions or subunits an entity possesses.
-
D.
parallelSubdivision
Indicates that one structure or process is divided into multiple parts that proceed or are handled simultaneously alongside each other.
-
E.
representsCurrentSubdivision
Indicates that one entity is the current administrative or organizational subdivision of another entity.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0680d51a4819098a6bcd3dfd73be4 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:32 p.m.