Triple
T10181916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brechin City F.C. |
E236805
|
entity |
| Predicate | hasHomeCapacity |
P78949
|
FINISHED |
| Object | approximately 4,000 |
—
|
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 4,000 | Statement: [Brechin City F.C., hasHomeCapacity, approximately 4,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHomeCapacity Context triple: [Brechin City F.C., hasHomeCapacity, approximately 4,000]
-
A.
hasHomeCapacityVenue
chosen
Indicates that a venue has a specified capacity for accommodating people or events as its home location.
-
B.
hasHomeFeature
Indicates that a home possesses or includes a particular feature or amenity.
-
C.
hasResidenceCapacityFor
Indicates that an entity’s residence can accommodate or provide living space for a specified number or type of occupants.
-
D.
hasCapacityTo
Indicates that one entity possesses the ability, power, or potential to perform an action or bring about a particular effect in relation to another entity or context.
-
E.
hasHomeSupport
Indicates that an entity receives assistance, backing, or favorable conditions from its home environment or local supporters.
- 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_69ca84d7260c8190bfbec36762943f37 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cded32b91c8190b01ad37b2456080a |
completed | April 2, 2026, 4:14 a.m. |
| PD | Predicate disambiguation | batch_69cd7c79f21c8190a7f31b2eab80b8ba |
completed | April 1, 2026, 8:13 p.m. |
Created at: March 30, 2026, 9:12 p.m.