Triple
T33812056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cros-ny-Cuirn |
E866561
|
entity |
| Predicate | stopType |
P25018
|
FINISHED |
| Object | request stop |
—
|
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: request stop | Statement: [Cros-ny-Cuirn, stopType, request stop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stopType Context triple: [Cros-ny-Cuirn, stopType, request stop]
-
A.
stoppedBy
Indicates that one entity causes another entity to cease moving, operating, or continuing an action.
-
B.
stopsPattern
Indicates that one entity halts, interrupts, or prevents the continuation of a recurring or structured pattern involving another entity.
-
C.
stopPolicy
Indicates that an entity terminates, cancels, or brings to an end a policy or ongoing course of action.
-
D.
hasStopType
chosen
Indicates that a stop or stopping point is classified as having a particular type or category of stop.
-
E.
stopsCharacteristic
Indicates that one entity has the characteristic or property of stopping or causing a stop in another entity or process.
- 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffcddfc08190bb83e4f2de5bee7b |
completed | May 3, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:46 a.m.