Triple
T37369389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voronwë |
E927795
|
entity |
| Predicate | laterSailsWith |
P203045
|
FINISHED |
| Object | Tuor |
—
|
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: Tuor | Statement: [Voronwë, laterSailsWith, Tuor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterSailsWith Context triple: [Voronwë, laterSailsWith, Tuor]
-
A.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
B.
sails
Indicates that an entity travels over water in a vessel propelled by sails or similar means.
-
C.
hasSail
Indicates that one entity possesses or is equipped with a sail used for catching wind.
-
D.
sailingUnder
Indicates that one entity (typically a vessel) is operating or traveling while registered, flagged, or officially recognized under the authority or jurisdiction of another entity (such as a country or organization).
-
E.
sailPlan
Indicates a plan or arrangement for how a vessel will be sailed, including intended route, timing, and sailing configuration.
- F. None of above. chosen
Provenance (4 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_69f76eb820248190a5c395ca50ad002a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01185c46f0819089b4a2ad3c3e2f33 |
completed | May 10, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_6a0117e19e008190870663dd45084416 |
completed | May 10, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_6a01185b580c8190a01f65404486cfec |
completed | May 10, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:16 p.m.