Triple
T13509346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lent Bumps |
E321094
|
entity |
| Predicate | hasFinishArea |
P47075
|
FINISHED |
| Object | near Jesus Lock |
—
|
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: near Jesus Lock | Statement: [Lent Bumps, hasFinishArea, near Jesus Lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishArea Context triple: [Lent Bumps, hasFinishArea, near Jesus Lock]
-
A.
finishingArea
chosen
Indicates the location or area where an activity, process, or event comes to an end or is completed.
-
B.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
C.
startFinishArea
Indicates a relationship where a defined area serves as both the starting point and the finishing point for an event, route, or activity.
-
D.
hasArrivalArea
Indicates that an entity is associated with a specific area designated for arrivals, such as where incoming people or items first enter or are received.
-
E.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
- 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_69d807629d6c8190998f1b9bb12d2ed0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaf85a74081909eb08751fc55ce8f |
completed | April 12, 2026, 2:43 p.m. |
| PD | Predicate disambiguation | batch_69dbae0b63748190b5e207f84b2532ea |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:43 p.m.