Triple
T29498843
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Republic of Noli |
E748310
|
entity |
| Predicate | seafaringPower |
P21383
|
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: [Republic of Noli, seafaringPower, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seafaringPower Context triple: [Republic of Noli, seafaringPower, true]
-
A.
navalPowerType
Indicates the classification of a naval force or capability according to its type or role within maritime power structures.
-
B.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
C.
navalPowerStatus
chosen
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
-
D.
navalPowerContext
Indicates a context in which an entity’s naval strength, capabilities, or influence is relevant to its relationships or actions with other entities.
-
E.
navalRatioPowers
Indicates the comparative balance of naval strength or power between entities, typically expressed as a ratio.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c3129508190aa6bbd520f4daea6 |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:21 p.m.