Triple
T11524930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seoul–Sydney |
E273267
|
entity |
| Predicate | crossesEquator |
P11761
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Seoul–Sydney, crossesEquator, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesEquator Context triple: [Seoul–Sydney, crossesEquator, true]
-
A.
hasEquatorCrossing
chosen
Indicates that the path or orbit of an entity crosses the equator of a reference body.
-
B.
hasTropicOfCapricornCrossing
Indicates that the referenced geographic entity is intersected or crossed by the Tropic of Capricorn.
-
C.
hasTropicOfCancerCrossing
Indicates that the specified entity is geographically intersected or crossed by the Tropic of Cancer.
-
D.
eclipticCrossing
Indicates that one object's path crosses the ecliptic plane at a specific point or during a specific event.
-
E.
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.
- 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_69d6aae3fbec8190a14632a5df2538b6 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d87fd379648190b342e0c4b4f685b7 |
completed | April 10, 2026, 4:42 a.m. |
| PD | Predicate disambiguation | batch_69d80876e5f0819088cff2e72f773cf6 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.