Triple
T32096024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Great Sea |
E819723
|
entity |
| Predicate | usedForVoyageBy |
P62903
|
FINISHED |
| Object | the Númenóreans |
—
|
NE NERFINISHED |
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: the Númenóreans | Statement: [the Great Sea, usedForVoyageBy, the Númenóreans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForVoyageBy Context triple: [the Great Sea, usedForVoyageBy, the Númenóreans]
-
A.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
B.
involvesVoyageFrom
Indicates a relationship where an event, action, or situation includes a voyage that originates from a specified starting location.
-
C.
usedWhenOnBoard
Indicates that something is employed or utilized while a person or object is on board a vehicle, vessel, or similar conveyance.
-
D.
usedForShips
Indicates that something is designed, intended, or suitable to be used for ships or ship-related purposes.
-
E.
bayUsedFor
chosen
Indicates that a bay or inlet serves a particular function or purpose, such as supporting a specific activity, use, or operation.
- 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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 12:26 a.m.