Triple
T977161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oscar and Lucinda |
E21078
|
entity |
| Predicate | outbackJourney |
P22096
|
FINISHED |
| Object | transporting a glass church across the Australian outback |
—
|
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: transporting a glass church across the Australian outback | Statement: [Oscar and Lucinda, outbackJourney, transporting a glass church across the Australian outback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: outbackJourney Context triple: [Oscar and Lucinda, outbackJourney, transporting a glass church across the Australian outback]
-
A.
typicalExpeditionMode
Indicates the usual or most common mode or method by which an expedition is conducted.
-
B.
explores
Indicates actively investigating, traveling through, or examining something in order to discover or learn more about it.
-
C.
coTraveler
Indicates that two or more entities are traveling together along (part of) the same journey or route.
-
D.
oftenCrossedOn
Indicates that one entity is frequently traversed or passed over by another entity.
-
E.
TrailLinkIs
Indicates that one trail segment is connected to or continues from another trail segment.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b46344048190b7a13b8f3ad9f455 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a8a3b08190b4538e119b13f7f5 |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b344f6f48190ba03ce593c94176b |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:40 p.m.