Triple
T7344248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gelykheid |
E169335
|
entity |
| Predicate | navalBattleRole |
P39666
|
FINISHED |
| Object | line-of-battle ship |
—
|
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: line-of-battle ship | Statement: [Gelykheid, navalBattleRole, line-of-battle ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalBattleRole Context triple: [Gelykheid, navalBattleRole, line-of-battle ship]
-
A.
navalTacticRole
chosen
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
B.
navalOperationsBy
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
C.
notableBattleRole
Indicates the specific role or function an entity played in a notable or historically significant battle.
-
D.
navalAnalogue
Indicates that one entity serves as the naval or maritime counterpart or equivalent of another entity in function, role, or classification.
-
E.
navalCommand
Indicates a relationship where one entity holds authority to direct, control, or oversee naval forces or maritime military operations involving another entity.
- 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_69c68a57710481909f0c1f3c6ebdb6f2 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f139505c8190a7158cf59a6e089e |
completed | March 27, 2026, 9:06 p.m. |
| PD | Predicate disambiguation | batch_69c6f02aeeb8819099d1626566cec18b |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:05 p.m.