Triple
T11047332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harad |
E261165
|
entity |
| Predicate | hasOrientationFromMordor |
P45984
|
FINISHED |
| Object | south and southwest |
—
|
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: south and southwest | Statement: [Harad, hasOrientationFromMordor, south and southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrientationFromMordor Context triple: [Harad, hasOrientationFromMordor, south and southwest]
-
A.
hasOrientation
Indicates that one entity is positioned or directed in a specific spatial or conceptual alignment relative to a reference frame or another entity.
-
B.
hasRegionalOrientation
chosen
Indicates that an entity is oriented toward, focused on, or primarily associated with a specific geographic region.
-
C.
hasFlukeOrientation
Indicates the orientation or positioning of a fluke relative to another reference object or axis.
-
D.
hasShoreOrientation
Indicates the directional orientation of a shoreline relative to a reference frame (e.g., compass direction or facing).
-
E.
hasFieldOrientation
Indicates that one entity has a specified directional or spatial orientation relative to a field (such as magnetic, electric, or visual field).
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798315b988190bc565581b2664009 |
completed | April 9, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69d74407cb088190ba37c8da3d342b64 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.