Triple
T32076105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Bee Cuddy |
E819154
|
entity |
| Predicate | journeyThrough |
P54144
|
FINISHED |
| Object | harsh frontier territory |
—
|
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: harsh frontier territory | Statement: [Mary Bee Cuddy, journeyThrough, harsh frontier territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyThrough Context triple: [Mary Bee Cuddy, journeyThrough, harsh frontier territory]
-
A.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
-
B.
journeysAcross
Indicates that an entity travels or moves from one side or area to another, passing over or through an intervening space or boundary.
-
C.
travelsThrough
chosen
Indicates that something moves along, passes across, or is routed via a particular path, medium, or location.
-
D.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
E.
journeyFunction
Indicates a relationship where an entity serves as the purpose, role, or functional objective of a journey or travel 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b52d33e08190ac04d0a50141d099 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:23 a.m.