Triple
T19416534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belisha beacon |
E485730
|
entity |
| Predicate | polePattern |
P8034
|
FINISHED |
| Object | black-and-white 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: black-and-white stripes | Statement: [Belisha beacon, polePattern, black-and-white stripes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: polePattern Context triple: [Belisha beacon, polePattern, black-and-white stripes]
-
A.
poleRepresentation
Indicates a representation of something in terms of its poles, typically expressing a system, function, or object using its pole-based form.
-
B.
patroonOf
Indicates a relationship in which one entity acts as a patron, sponsor, or protector providing support or resources to another entity.
-
C.
pattern
chosen
Indicates that one entity exhibits, follows, or is characterized by a particular recurring form, structure, or arrangement associated with another entity.
-
D.
pole
Indicates that one entity is a long, slender, typically vertical support or rod associated with or used by another entity.
-
E.
wingPattern
Indicates the characteristic arrangement or design present on an entity's wings.
- 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62af9c8fc81909860de10b6720207 |
completed | April 20, 2026, 1:32 p.m. |
| PD | Predicate disambiguation | batch_69e4fd68b1f881908d273de1fee81a75 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:37 p.m.