Triple
T33879333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mossos d'Esquadra |
E868441
|
entity |
| Predicate | vehicleMarking |
P171798
|
FINISHED |
| Object | blue and white with red stripes |
—
|
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: blue and white with red stripes | Statement: [Mossos d'Esquadra, vehicleMarking, blue and white with red stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vehicleMarking Context triple: [Mossos d'Esquadra, vehicleMarking, blue and white with red stripes]
-
A.
coatMarkings
Indicates how an entity’s coat is patterned or marked, such as stripes, spots, or other distinctive visual markings.
-
B.
armorMarkings
Indicates that one entity bears specific markings, patterns, or insignia on its armor in relation to another entity or context.
-
C.
colorOfTrailMarkings
Indicates the relationship specifying what color the trail’s markings are.
-
D.
aircraftMarking
Indicates a relationship where a marking, symbol, or identifier is applied to or displayed on an aircraft.
-
E.
colorMarkings
chosen
Indicates that one entity has specific color-based markings or patterns in relation to 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.