Triple
T2321583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nazca Ridge |
E51192
|
entity |
| Predicate | orientedApproximately |
P29149
|
FINISHED |
| Object | northwest–southeast |
—
|
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: northwest–southeast | Statement: [Nazca Ridge, orientedApproximately, northwest–southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientedApproximately Context triple: [Nazca Ridge, orientedApproximately, northwest–southeast]
-
A.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
B.
orientationProperty
chosen
Indicates that one entity has a specific spatial or directional orientation in relation to another entity or reference frame.
-
C.
socialOrientation
Indicates the nature or direction of an entity’s social tendencies, such as how it typically relates to, interacts with, or aligns itself within social contexts or groups.
-
D.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
E.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc5909cc48190aab257313542dc49 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:49 p.m.