Triple
T6369750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nettie |
E143316
|
entity |
| Predicate | journeyFunction |
P70241
|
FINISHED |
| Object | broadens story’s geographic scope |
—
|
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: broadens story’s geographic scope | Statement: [Nettie, journeyFunction, broadens story’s geographic scope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: journeyFunction Context triple: [Nettie, journeyFunction, broadens story’s geographic scope]
-
A.
journeyFrom
Indicates that an entity undertakes or originates a journey starting from a specified location or source.
-
B.
journey
Indicates that an entity travels or moves from one place or state to another, typically over a period of time or distance.
-
C.
journeyDestination
Indicates that one entity serves as the endpoint or intended destination of another entity’s journey or travel.
-
D.
sunJourneyPurpose
Indicates the purpose or intended goal behind a sun-related journey or movement.
-
E.
journeysAcross
Indicates that an entity travels or moves from one side or area to another, passing over or through an intervening space or boundary.
- F. None of above. chosen
Provenance (4 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_69c008d8c61081908bcaf61510d881ed |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c068265a7481908571be7ea4ac11b7 |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623d23448190a75cf5d802fc0a02 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:33 p.m.