Triple
T13814691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | flag of Slovenia |
E331983
|
entity |
| Predicate | starsOrigin |
P111595
|
FINISHED |
| Object | coat of arms of the Counts of Celje |
—
|
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: coat of arms of the Counts of Celje | Statement: [flag of Slovenia, starsOrigin, coat of arms of the Counts of Celje]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: starsOrigin Context triple: [flag of Slovenia, starsOrigin, coat of arms of the Counts of Celje]
-
A.
originalStar
Indicates that one entity is the initial or primary star from which another star or stellar object originates, is derived, or is otherwise based.
-
B.
starKnownAs
Indicates that a particular star is referred to or identified by a specific name or designation.
-
C.
starIs
Indicates that one entity is identified or classified as a star in relation to another entity or context.
-
D.
stars
Indicates that one entity marks, highlights, or designates another as special, important, or featured (often by assigning a star or similar marker).
-
E.
starType
Indicates the classification relationship specifying what type or category of star an astronomical object is.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02806e148190996f58934e66d7d8 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
| PDg | Predicate description generation | batch_69dcad0eea9881908f71e1eed9a2446b |
completed | April 13, 2026, 8:45 a.m. |
Created at: April 9, 2026, 10:12 p.m.