Triple
T36909564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oakland Raiders Hall of Fame |
E912870
|
entity |
| Predicate | isOfficialHonorOf |
P92060
|
FINISHED |
| Object | Raiders franchise |
—
|
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: Raiders franchise | Statement: [Oakland Raiders Hall of Fame, isOfficialHonorOf, Raiders franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOfficialHonorOf Context triple: [Oakland Raiders Hall of Fame, isOfficialHonorOf, Raiders franchise]
-
A.
isHonor
chosen
Indicates that one entity is regarded as an honor, distinction, or source of prestige for another entity.
-
B.
honourOf
Indicates that one entity is the source, bearer, or cause of another entity’s honor, prestige, or distinguished recognition.
-
C.
areOfficialIn
Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
-
D.
hasCodeOfHonor
Indicates that an entity adheres to a personal or shared ethical code that guides its behavior and decisions.
-
E.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
- 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fdadf6bc81908add47081b004503 |
completed | May 5, 2026, 2:24 p.m. |
| PD | Predicate disambiguation | batch_69f7cf79ddb08190a083405cccc14137 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.