Triple
T33829012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East Stand |
E867043
|
entity |
| Predicate | isAccessedDuring |
P105323
|
FINISHED |
| Object | Hibernian FC home fixtures |
—
|
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: Hibernian FC home fixtures | Statement: [East Stand, isAccessedDuring, Hibernian FC home fixtures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessedDuring Context triple: [East Stand, isAccessedDuring, Hibernian FC home fixtures]
-
A.
isAccessibleDuring
chosen
Indicates that one entity can be reached, used, or entered during the time period, event, or condition specified by another entity.
-
B.
accessedAfter
Indicates that one entity is accessed only after another entity has already been accessed in time or sequence.
-
C.
accessedThrough
Indicates that one entity is reached, used, or obtained by means of another entity that serves as an intermediary channel, tool, or pathway.
-
D.
checkedDuring
Indicates that an entity was examined, inspected, or verified at a specific time or during a particular event or process.
-
E.
laterAccessedBy
Indicates that an entity is subsequently accessed or used by another entity at a later point in time.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002143188190aed5ea871608fbc5 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.