Triple
T17245098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montrose F.C. |
E418601
|
entity |
| Predicate | hasHomeStadiumCapacity |
P3507
|
FINISHED |
| Object | approximately 4000 |
—
|
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: approximately 4000 | Statement: [Montrose F.C., hasHomeStadiumCapacity, approximately 4000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeStadiumCapacity Context triple: [Montrose F.C., hasHomeStadiumCapacity, approximately 4000]
-
A.
homeStadiumCapacity
chosen
Indicates the seating capacity of the stadium that serves as a team's or organization's home venue.
-
B.
cityStadiumCapacity
Indicates the maximum number of spectators that a given city’s stadium can accommodate.
-
C.
hasHomeCapacityVenue
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
D.
stadiumCapacityApprox
Indicates an approximate number of people that a stadium can accommodate.
-
E.
hasHomeStadiumContext
Indicates that an entity’s home stadium is specified or characterized within a particular contextual framework (such as time, competition, or role).
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e22fb2c8190aea5d3872095bf46 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.