Triple
T3962297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace Line |
E85932
|
entity |
| Predicate | passesBetween |
P15632
|
FINISHED |
| Object | Bali and Lombok |
—
|
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: Bali and Lombok | Statement: [Wallace Line, passesBetween, Bali and Lombok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: passesBetween Context triple: [Wallace Line, passesBetween, Bali and Lombok]
-
A.
runsBetween
chosen
Indicates a relationship where something extends, operates, or connects from one point, entity, or state to another along a path or interval.
-
B.
passesUnder
Indicates that one entity moves or extends beneath another entity, typically crossing below it without direct contact.
-
C.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
-
D.
usedBetween
Indicates that something serves as a means, medium, or shared resource connecting or operating jointly between two entities.
-
E.
meetsBetween
Indicates that one entity meets or encounters another at some point between two specified reference points or times.
- 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefba878a48190a2e234d775215938 |
completed | March 9, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69aef8efcf3c81908ccf61d9ce26b0c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:31 p.m.