Triple
T28410569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moesian fleet |
E719650
|
entity |
| Predicate | typeOfWatercraftUsed |
P197387
|
FINISHED |
| Object | river warships |
—
|
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: river warships | Statement: [Moesian fleet, typeOfWatercraftUsed, river warships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWatercraftUsed Context triple: [Moesian fleet, typeOfWatercraftUsed, river warships]
-
A.
boatRole
Indicates the specific function, duty, or position an entity has in relation to a boat within a given context.
-
B.
boatTypeAllowed
Indicates that a specified type of boat is permitted or authorized in a given context or location.
-
C.
boatTraveledOn
Indicates that a boat moved or was transported along or across a specified body of water or route.
-
D.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
E.
boatCapability
Indicates that one entity has the capability or suitability to function as a boat for another entity or purpose.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
| PDg | Predicate description generation | batch_69fe8f730bb88190975bffd49f5e0f3b |
completed | May 9, 2026, 1:35 a.m. |
Created at: April 28, 2026, 1:26 a.m.