Triple
T4271756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stirling Albion F.C. |
E96955
|
entity |
| Predicate | movedToCurrentGround |
P42451
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Stirling Albion F.C., movedToCurrentGround, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToCurrentGround Context triple: [Stirling Albion F.C., movedToCurrentGround, 1993]
-
A.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
-
B.
movementLocation
chosen
Indicates a relationship where an entity moves to, from, or through a specified location.
-
C.
usesGroundSystem
Indicates that one entity operates, relies on, or interacts with a particular ground-based system to perform its functions or services.
-
D.
movementContext
Indicates the situational or environmental conditions under which a movement or motion event occurs, such as its manner, setting, or constraints.
-
E.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
- 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffce3d8819083d2278547fa52c1 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.