Triple
T16355777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhein Fire |
E397174
|
entity |
| Predicate | homeAttendanceRecord |
P123101
|
FINISHED |
| Object | among highest in NFL Europe |
—
|
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: among highest in NFL Europe | Statement: [Rhein Fire, homeAttendanceRecord, among highest in NFL Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAttendanceRecord Context triple: [Rhein Fire, homeAttendanceRecord, among highest in NFL Europe]
-
A.
homeAttendanceCharacteristic
Indicates a characteristic or attribute related to the attendance of individuals in a home or household setting.
-
B.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
C.
attendanceUnit
Indicates a unit or measure used to quantify or record attendance in a given context.
-
D.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
E.
attendanceIssues
Indicates that there are problems or irregularities related to an entity’s attendance, such as frequent absences, tardiness, or non-compliance with attendance expectations.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2face3a54819099418edd0eecc963 |
completed | April 18, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69e226f37ecc819082af58b29b4e39d1 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:07 a.m.