Triple
T31186528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow Warriors |
E795057
|
entity |
| Predicate | homeGroundTenureStart |
P71101
|
FINISHED |
| Object | 2012s (Scotstoun Stadium) |
—
|
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: 2012s (Scotstoun Stadium) | Statement: [Glasgow Warriors, homeGroundTenureStart, 2012s (Scotstoun Stadium)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeGroundTenureStart Context triple: [Glasgow Warriors, homeGroundTenureStart, 2012s (Scotstoun Stadium)]
-
A.
leaseBegan
Indicates that a lease agreement between parties started or came into effect at a specific time.
-
B.
usedAsOfficialResidenceSince
Indicates that an entity has served as the formally designated official residence of another entity starting from a specified point in time.
-
C.
primaryTenantUntil
Indicates that an entity serves as the main or principal tenant of a property or lease up to a specified end date.
-
D.
landTenure
Indicates the type, conditions, or rights under which land is held, used, or owned by an entity.
-
E.
occupationDate
chosen
Indicates the date or time period during which an entity assumes, holds, or begins a particular role, position, or occupation.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.