Triple
T34513017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marist College Ashgrove |
E886073
|
entity |
| Predicate | hasRugbyFields |
P106710
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Marist College Ashgrove, hasRugbyFields, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRugbyFields Context triple: [Marist College Ashgrove, hasRugbyFields, true]
-
A.
hasRugbyGround
chosen
Indicates that an entity possesses, contains, or is associated with a rugby ground as a facility or location.
-
B.
hasSportsGround
Indicates that an entity possesses, includes, or is associated with a sports ground or athletic field as part of its facilities or area.
-
C.
hasCricketGround
Indicates that one entity possesses, contains, or includes a cricket ground as part of its facilities or attributes.
-
D.
hasLocalFootballGround
Indicates that a place or organization possesses or is associated with a nearby football ground used for local matches or activities.
-
E.
hasRugbyReputation
Indicates that an entity is recognized or regarded for its involvement, performance, or standing in rugby.
- 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_69f349ccc290819089d8e82698e53cb6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: May 1, 2026, 2:01 a.m.