Triple
T7214600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montrose Links |
E149498
|
entity |
| Predicate | isContinuouslyPlayed |
P28838
|
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: [Montrose Links, isContinuouslyPlayed, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isContinuouslyPlayed Context triple: [Montrose Links, isContinuouslyPlayed, true]
-
A.
playedUntil
Indicates that an action or event involving playing continued up to a specific time, point, or condition.
-
B.
isOngoing
chosen
Indicates that an action, process, or state is currently in progress and has not yet been completed or concluded.
-
C.
continuesToControl
Indicates that one entity maintains ongoing authority, influence, or command over another entity or resource over time.
-
D.
isNonstopPossible
Indicates that it is possible to perform or complete the referenced trip, route, or process without any intermediate stops or interruptions.
-
E.
isAnimated
Indicates that an entity possesses animation, meaning it is depicted or realized through moving images rather than static or live-action form.
- 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_69c687eca814819095abb52316b1af80 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e98cbebc8190941e76259c988790 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.