Triple
T24946789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders shield logo |
E624204
|
entity |
| Predicate | hasOutline |
P40118
|
FINISHED |
| Object | white border around shield |
—
|
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: white border around shield | Statement: [Raiders shield logo, hasOutline, white border around shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutline Context triple: [Raiders shield logo, hasOutline, white border around shield]
-
A.
hasContourLines
Indicates that an entity (such as a map or geographic representation) includes contour lines depicting elevation or terrain shape.
-
B.
hasNotableSketch
Indicates that an entity is associated with a sketch that is considered notable or significant in some context.
-
C.
hasStraightLines
Indicates that the related entity possesses or is characterized by straight, non-curved lines.
-
D.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
E.
hasSilhouetteShape
chosen
Indicates that one entity has the overall outline or contour shape specified or characterized by 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f423fcc11081909db3b69987693cd7 |
completed | May 1, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69f4210130d08190ae30b7943f7a0bbc |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:54 a.m.