Triple
T18580820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaii Islanders |
E454107
|
entity |
| Predicate | attendanceIssue |
P108418
|
FINISHED |
| Object | distanceFromMainland |
—
|
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: distanceFromMainland | Statement: [Hawaii Islanders, attendanceIssue, distanceFromMainland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attendanceIssue Context triple: [Hawaii Islanders, attendanceIssue, distanceFromMainland]
-
A.
attendanceIssues
chosen
Indicates that there are problems or irregularities related to an entity’s attendance, such as frequent absences, tardiness, or non-compliance with attendance expectations.
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
D.
attendanceUnit
Indicates a unit or measure used to quantify or record attendance in a given context.
-
E.
attendancePromotion
Indicates a relationship where one entity promotes, encourages, or incentivizes attendance at an event, activity, or location for 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cf33288190bc2cd6b7befde944 |
completed | April 19, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:43 a.m.