Triple
T8059556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic F.C. |
E188084
|
entity |
| Predicate | homeAttendanceCharacteristic |
P80286
|
FINISHED |
| Object | high average attendances |
—
|
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: high average attendances | Statement: [Celtic F.C., homeAttendanceCharacteristic, high average attendances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeAttendanceCharacteristic Context triple: [Celtic F.C., homeAttendanceCharacteristic, high average attendances]
-
A.
homeOrAway
Indicates whether an entity is acting in its own location (home) or in another’s location (away) within a given context.
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
D.
hasHumanPresence
Indicates that humans are physically present in or occupying a given location, object, or context.
-
E.
hasHouseholdFeature
Indicates that a household possesses or includes a specific feature, attribute, or amenity.
- 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_69ca82b2f68881908c50560697e210da |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3fcaa8b8819099267564b6542547 |
completed | March 31, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:25 p.m.