Triple
T18264193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bouvier des Flandres |
E437439
|
entity |
| Predicate | groupFCI |
P60921
|
FINISHED |
| Object | Group 1: Sheepdogs and Cattle Dogs |
—
|
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: Group 1: Sheepdogs and Cattle Dogs | Statement: [Bouvier des Flandres, groupFCI, Group 1: Sheepdogs and Cattle Dogs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groupFCI Context triple: [Bouvier des Flandres, groupFCI, Group 1: Sheepdogs and Cattle Dogs]
-
A.
groupInFCI
chosen
Indicates that an entity is a member of, or belongs to, a specific group within the FCI context.
-
B.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
-
C.
groupFunction
Indicates that an entity serves a specific role, purpose, or function within a group or collective context.
-
D.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
E.
coveredGroup
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff78b188819081da8e1d389c6c79 |
completed | April 19, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69e44fcdee748190bae6fb76e0cb22f3 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.