Triple
T24946771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders shield logo |
E624204
|
entity |
| Predicate | associatedWithFormerCity |
P174317
|
FINISHED |
| Object | Oakland |
—
|
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: Oakland | Statement: [Raiders shield logo, associatedWithFormerCity, Oakland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithFormerCity Context triple: [Raiders shield logo, associatedWithFormerCity, Oakland]
-
A.
hasAssociatedCityFormerName
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
-
B.
associatedWithCityHistory
Indicates a relationship where something is connected or relevant to the historical events, development, or heritage of a particular city.
-
C.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
-
D.
previouslyContainedCity
Indicates that one location used to include a particular city within its boundaries or jurisdiction at some time in the past, but no longer does.
-
E.
hasOldCity
Indicates that an entity possesses or contains an old or historic city as part of its domain or structure.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
| PDg | Predicate description generation | batch_69f6c125695c81909704c67bef4ce5b2 |
completed | May 3, 2026, 3:29 a.m. |
Created at: April 18, 2026, 5:54 a.m.