Triple
T4399322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pentarchy |
E99572
|
entity |
| Predicate | EasternView |
P55455
|
FINISHED |
| Object | primacy of honor without universal jurisdiction |
—
|
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: primacy of honor without universal jurisdiction | Statement: [Pentarchy, EasternView, primacy of honor without universal jurisdiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EasternView Context triple: [Pentarchy, EasternView, primacy of honor without universal jurisdiction]
-
A.
northernFrontier
Indicates that one entity serves as the northern boundary, edge, or frontier region relative to another entity.
-
B.
westernContinuation
Indicates that one entity is the western extension or continuation of another entity in space or geography.
-
C.
RockefellerForest
Indicates a relationship where something is located in, associated with, or part of Rockefeller Forest.
-
D.
region1
Indicates that one entity is the first or primary region associated with, containing, or encompassing another entity.
-
E.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
- F. None of above. chosen
Provenance (4 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352cc4ab081908bc45d2f76cd4da8 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff7018c81908ad8597e525c042b |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:20 p.m.