Triple
T18470949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Stand |
E451297
|
entity |
| Predicate | structuralRelation |
P84787
|
FINISHED |
| Object | faces the pitch at Fratton Park |
—
|
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: faces the pitch at Fratton Park | Statement: [South Stand, structuralRelation, faces the pitch at Fratton Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: structuralRelation Context triple: [South Stand, structuralRelation, faces the pitch at Fratton Park]
-
A.
subjectRelation
chosen
Indicates that one entity stands in a specified relational role or connection to another entity.
-
B.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
C.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
D.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
E.
stageRelation
Indicates a relationship between entities based on their roles, positions, or phases within a staged process or sequence.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5305f428c81909980bd30d150e7dd |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:34 a.m.