Triple
T35012319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyandonea |
E1009964
|
entity |
| Predicate | navalReputation |
P21383
|
FINISHED |
| Object | home of formidable Maormer fleets |
—
|
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: home of formidable Maormer fleets | Statement: [Pyandonea, navalReputation, home of formidable Maormer fleets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalReputation Context triple: [Pyandonea, navalReputation, home of formidable Maormer fleets]
-
A.
navalRating
Indicates the assessed level of naval strength, capability, or performance attributed to an entity.
-
B.
navalName
Indicates that an entity has a specific name used in a naval or maritime context.
-
C.
navalCountry
Indicates that a country possesses or operates a navy, signifying its involvement in naval or maritime military activities.
-
D.
navalAffiliation
Indicates a formal relationship in which an entity is associated with, belongs to, or operates under a particular navy or naval force.
-
E.
navalPowerStatus
chosen
Indicates the relative strength, capability, or strategic standing of an entity’s naval forces compared to others or to defined benchmarks.
- 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_69f76dcc3ac8819096a3ed52f5fa2523 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7858aa5508190a07dde993b3356fc |
completed | May 3, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69f7841812f081909d878955d114088e |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.