Triple
T33411213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana |
E855587
|
entity |
| Predicate | isPopularInEra |
P176566
|
FINISHED |
| Object | swing era |
—
|
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: swing era | Statement: [Indiana, isPopularInEra, swing era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularInEra Context triple: [Indiana, isPopularInEra, swing era]
-
A.
popularInCentury
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
B.
isPopularAs
Indicates that an entity is widely liked, well-known, or favored in a particular role, context, or capacity.
-
C.
hasEraInfluence
Indicates that one era or time period has a significant impact on shaping the characteristics, developments, or outcomes of another.
-
D.
isBsideOfEra
Indicates that one entity is the B-side counterpart associated with a particular era of another entity (such as a primary release or period).
-
E.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
- F. None of above. chosen
Provenance (4 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e52a6d40819084472f6072c91e9f |
completed | May 3, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69f6e3da41948190a4cfe866ce184f73 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e47c13348190a10528c84a401178 |
completed | May 3, 2026, 6 a.m. |
Created at: May 1, 2026, 1:36 a.m.