Triple
T5407022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Othrys |
E120916
|
entity |
| Predicate | warRole |
P9463
|
FINISHED |
| Object | military base of the Titans |
—
|
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: military base of the Titans | Statement: [Mount Othrys, warRole, military base of the Titans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: warRole Context triple: [Mount Othrys, warRole, military base of the Titans]
-
A.
warSecretary
Indicates that one entity serves as the war secretary (or secretary of war/defense) of another entity, typically a government or state.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
warfareType
Indicates the specific kind or category of warfare that characterizes a given conflict or military engagement.
-
D.
militaryFunction
Indicates a relationship where an entity serves a specific role, duty, or operational purpose within a military context.
-
E.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8793ab3c81909992b257d462a554 |
completed | March 20, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69bd8467e6b48190b9eaa9de67072e06 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.