Triple
T23226319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eagle of the Sea |
E581022
|
entity |
| Predicate | featuresSeafaringAction |
P48624
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Eagle of the Sea, featuresSeafaringAction, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresSeafaringAction Context triple: [The Eagle of the Sea, featuresSeafaringAction, true]
-
A.
navalFeatures
Indicates that something possesses characteristics, components, or attributes specifically associated with naval or maritime contexts.
-
B.
featuresVessel
Indicates that one entity includes, presents, or prominently displays a particular vessel as part of its composition, content, or configuration.
-
C.
featuresPirates
Indicates that something includes or prominently involves pirates as part of its content or subject matter.
-
D.
hasSeafaringTheme
chosen
Indicates that something is characterized by or prominently features elements related to seafaring, such as ships, sailors, or maritime life.
-
E.
shipFeatured
Indicates that a particular ship is highlighted or promoted as a featured item in a given context.
- 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_69e246043c48819089bae72c9a9c306c |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f1922e2d2c81908c0f3fa5df8a5c58 |
completed | April 29, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.