Triple
T24656537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajaraja I |
E610406
|
entity |
| Predicate | launchedNavalCampaign |
P68244
|
FINISHED |
| Object | in the Arabian Sea |
—
|
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: in the Arabian Sea | Statement: [Rajaraja I, launchedNavalCampaign, in the Arabian Sea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedNavalCampaign Context triple: [Rajaraja I, launchedNavalCampaign, in the Arabian Sea]
-
A.
navalVictoryOver
Indicates that one party has defeated another in a military engagement at sea.
-
B.
militaryCampaignOf
Indicates a relationship where a specific military campaign is conducted by, initiated by, or belongs to a particular military force, state, or commander.
-
C.
navalOperationsBy
chosen
Indicates that a set of naval operations is conducted, controlled, or carried out by a specified agent or organization.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 2:34 a.m.