Triple
T19416550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belisha beacon |
E485730
|
entity |
| Predicate | standardColorOfGlobe |
P135792
|
FINISHED |
| Object | amber |
—
|
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: amber | Statement: [Belisha beacon, standardColorOfGlobe, amber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardColorOfGlobe Context triple: [Belisha beacon, standardColorOfGlobe, amber]
-
A.
traditionalKitColor
Indicates the customary or historically established color scheme used for an entity’s standard or primary kit or uniform.
-
B.
centralStarColor
Indicates the color characteristic of a system’s central star in the relationship.
-
C.
mapColor
Indicates a relationship where a map region or area is assigned or associated with a specific color, typically for visualization or categorization purposes.
-
D.
nationalColorsRepresented
Indicates that the national colors of an entity are visibly included or symbolically expressed in another entity or context.
-
E.
cereColor
Indicates that one entity specifies or denotes the color of another entity’s cere (the fleshy area above a bird’s beak).
- 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_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. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:37 p.m.