Triple
T29402194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster City F.C. |
E745673
|
entity |
| Predicate | hasHomeGroundSince |
P55191
|
FINISHED |
| Object | Giant Axe |
—
|
NE NERFINISHED |
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: Giant Axe | Statement: [Lancaster City F.C., hasHomeGroundSince, Giant Axe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeGroundSince Context triple: [Lancaster City F.C., hasHomeGroundSince, Giant Axe]
-
A.
homeFieldSince
Indicates that a particular location has served as the designated home field or home venue for an entity starting from a specified point in time.
-
B.
previousHomeGroundLocatedIn
Indicates that the location specified is where an entity’s former or earlier home ground was situated.
-
C.
isHomeGroundSince
chosen
Indicates that a particular location has served as the designated home ground of an entity (such as a team or organization) starting from a specified point in time.
-
D.
stateOfHomeGround
Indicates the location or region that serves as an entity’s primary home ground or base of operations.
-
E.
denotesHomeGroundOf
Indicates that a particular location serves as the primary home ground or home venue for a specified team, organization, or 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 2:51 p.m.