Triple
T36557953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Western Sea |
E901743
|
entity |
| Predicate | hasDirectionDescriptor |
P117258
|
FINISHED |
| Object | western |
—
|
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: western | Statement: [The Western Sea, hasDirectionDescriptor, western]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionDescriptor Context triple: [The Western Sea, hasDirectionDescriptor, western]
-
A.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
B.
hasDirectionReference
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
C.
hasDirectionCode
Indicates that something is associated with a specific standardized code representing its direction or orientation.
-
D.
hasDirectionInName
chosen
Indicates that the entity’s name explicitly contains a directional term (e.g., north, south, east, west, or similar).
-
E.
hasDirectionScheme
Indicates that an entity is associated with or governed by a particular scheme or system for defining directions.
- 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff63e6b61081909c648bf0ff279481 |
completed | May 9, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69ff6381867881908ae0545df4b71df5 |
completed | May 9, 2026, 4:40 p.m. |
Created at: May 3, 2026, 4:11 p.m.