Triple
T22486320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntsville 1996 |
E555888
|
entity |
| Predicate | featuresLiveAudience |
P134836
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Huntsville 1996, featuresLiveAudience, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLiveAudience Context triple: [Huntsville 1996, featuresLiveAudience, true]
-
A.
liveAudiencePresent
chosen
Indicates that a live, physically present audience is attending the event or performance.
-
B.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
C.
associatedMusicAudience
Indicates a relationship where a piece of music, musical work, or performance is intended for, targeted at, or commonly associated with a particular audience or listener group.
-
D.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3c6d808190b6dc70c3d1985bf3 |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.