Triple
T29957639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arena |
E760948
|
entity |
| Predicate | typicalEnergyLevel |
P154451
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [The Arena, typicalEnergyLevel, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEnergyLevel Context triple: [The Arena, typicalEnergyLevel, high]
-
A.
typicalLowestLevel
Indicates that something represents the most basic or minimal level that is commonly or normally found within a given context.
-
B.
typicalHighestLevel
Indicates the usual or most common maximum level or degree that something typically reaches within a given context.
-
C.
typicalDynamicLevel
chosen
Indicates the usual or characteristic intensity or volume level at which an action, event, or interaction typically occurs.
-
D.
typicalPower
Indicates the usual or characteristic amount of power associated with an entity under normal operating conditions.
-
E.
typicalEnergyRange
Indicates the usual or characteristic range of energy values associated with an entity, process, or interaction.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a0317eaf4e88190a6f6419cb4ef7547 |
completed | May 12, 2026, 12:07 p.m. |
| PD | Predicate disambiguation | batch_6a03179da394819095e3d346c3785d74 |
completed | May 12, 2026, 12:05 p.m. |
Created at: April 29, 2026, 6:27 p.m.