Triple
T3078489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guillaume Tell |
E64196
|
entity |
| Predicate | militaryClassification |
P28510
|
FINISHED |
| Object | ship of the line |
—
|
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: ship of the line | Statement: [Guillaume Tell, militaryClassification, ship of the line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryClassification Context triple: [Guillaume Tell, militaryClassification, ship of the line]
-
A.
hasMilitaryDesignation
chosen
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
B.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
-
C.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
D.
militaryDomain
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
E.
militaryCharacteristic
Indicates that one entity possesses a specific military-related attribute, quality, or feature in relation to another entity or 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a86a848190a47ca127cc7e6326 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:02 p.m.