Triple
T28556864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Legion of Boom defense era |
E723029
|
entity |
| Predicate | noiseAdvantage |
P7339
|
FINISHED |
| Object | home crowd noise at CenturyLink Field |
—
|
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: home crowd noise at CenturyLink Field | Statement: [Legion of Boom defense era, noiseAdvantage, home crowd noise at CenturyLink Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: noiseAdvantage Context triple: [Legion of Boom defense era, noiseAdvantage, home crowd noise at CenturyLink Field]
-
A.
notableAdvantage
chosen
Indicates that one entity possesses a significant benefit, edge, or favorable quality over another entity or in a given context.
-
B.
noiseLevel
Indicates the intensity or amount of sound present in a given environment or from a specific source.
-
C.
neutralAttackFeature
Indicates that an entity has the capability to perform an attack that is neutral, i.e., not aligned with any particular side, type, or affinity.
-
D.
noisePolicy
Indicates the rules or constraints governing acceptable noise levels or noise-related behavior in a given context.
-
E.
advantageOverEcho
Indicates that one entity possesses an advantage or superiority over another entity referred to as Echo.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f6505097348190b46266efd9cd007d |
completed | May 2, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:46 a.m.