Triple
T19574282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaii Hawaiians |
E489809
|
entity |
| Predicate | operatedDuringSeason |
P802
|
FINISHED |
| Object | 1974 WFL season |
—
|
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: 1974 WFL season | Statement: [Hawaii Hawaiians, operatedDuringSeason, 1974 WFL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedDuringSeason Context triple: [Hawaii Hawaiians, operatedDuringSeason, 1974 WFL season]
-
A.
operatedSeason
Indicates the specific season or time period during which an entity (such as a service, facility, or operation) was active or in use.
-
B.
occurredInSeason
Indicates that an event or occurrence took place during a specific season within a temporal sequence (such as a TV show season or sports season).
-
C.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
D.
runsInSeason
Indicates that an activity, event, or process occurs during a specified season or seasonal period.
-
E.
isAiredDuring
Indicates that an event, program, or broadcast takes place within a specified time period or schedule.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402333dc8190bdffb1da68e2c76b |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.