Triple
T10842427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Force |
E255921
|
entity |
| Predicate | relativeDirection |
P73279
|
FINISHED |
| Object | approached Leyte Gulf from the south |
—
|
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: approached Leyte Gulf from the south | Statement: [Southern Force, relativeDirection, approached Leyte Gulf from the south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeDirection Context triple: [Southern Force, relativeDirection, approached Leyte Gulf from the south]
-
A.
directionRelativeTo
chosen
Indicates the spatial orientation of one entity in relation to another, such as which way it faces or points relative to a reference entity.
-
B.
relativePosition
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
C.
relativeMotionType
Indicates the type or nature of motion occurring between two entities relative to one another.
-
D.
offsetDirection
Indicates the relative direction in which one entity is displaced or shifted from another reference entity.
-
E.
directionalRole
Indicates a role or function defined in terms of a direction or orientation relative to another entity or reference frame.
- 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_69d6aa81a5d08190aa86689061d1ddd2 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d750ce40108190895c477553195fe4 |
completed | April 9, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d70d25280c8190b648d7d1958b413a |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:19 p.m.