Triple
T35740067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forest's Elbow |
E1033008
|
entity |
| Predicate | leadsOnto |
P24175
|
FINISHED |
| Object | Conrod Straight |
—
|
NE NERFINISHED |
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: Conrod Straight | Statement: [Forest's Elbow, leadsOnto, Conrod Straight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadsOnto Context triple: [Forest's Elbow, leadsOnto, Conrod Straight]
-
A.
leadsInto
chosen
Indicates that one entity serves as an entry or transition point that directly connects or opens into another entity.
-
B.
leadsAstray
Indicates that one entity causes another entity to deviate from a correct, moral, or intended path or course of action.
-
C.
leadsEyeToward
Indicates that one entity directs or guides the viewer’s gaze in the direction of another entity.
-
D.
canLeadTo
Indicates that one entity, condition, or event has the potential to cause, result in, or bring about another.
-
E.
leads
Indicates having primary responsibility for directing, guiding, or managing another entity or group toward a goal or outcome.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.