Triple
T31853014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volante (uniformed patrol units) |
E813115
|
entity |
| Predicate | visibleMarking |
P99152
|
FINISHED |
| Object | word "Polizia" on vehicles |
—
|
NE NERFINISHED |
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: word "Polizia" on vehicles | Statement: [Volante (uniformed patrol units), visibleMarking, word "Polizia" on vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visibleMarking Context triple: [Volante (uniformed patrol units), visibleMarking, word "Polizia" on vehicles]
-
A.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
B.
markingFeature
chosen
Indicates a feature that serves as a distinguishing mark or identifier associated with an entity.
-
C.
marked
Indicates that one entity has been identified, labeled, or highlighted in some way by another entity.
-
D.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
E.
colorMarkings
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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03f3b148190a1b096da2a6c5864 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:51 p.m.