Triple
T6856057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raiders |
E158145
|
entity |
| Predicate | teamReputation |
P49959
|
FINISHED |
| Object | physical and aggressive style of play |
—
|
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: physical and aggressive style of play | Statement: [Raiders, teamReputation, physical and aggressive style of play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamReputation Context triple: [Raiders, teamReputation, physical and aggressive style of play]
-
A.
scoringReputation
Indicates that one entity evaluates and assigns a reputation-related score to another entity based on its behavior or performance.
-
B.
crowdReputation
chosen
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
C.
internationalReputation
Indicates the recognized standing, esteem, or status an entity holds within the global or international community.
-
D.
institutionalReputationContext
Indicates the situational or environmental factors that shape or influence an institution’s reputation.
-
E.
liveReputation
Indicates a dynamic, continuously updated assessment of an entity’s standing, trustworthiness, or performance based on recent or real-time information.
- 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_69c6882fae988190864cbba788c5ebb4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:20 p.m.