Triple
T6987110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negusa Nagast |
E161990
|
entity |
| Predicate | relatedConcept |
P37
|
FINISHED |
| Object | Imperator |
E57368
|
NE 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: Imperator | Statement: [Negusa Nagast, relatedConcept, Imperator]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Imperator Context triple: [Negusa Nagast, relatedConcept, Imperator]
-
A.
Imperator
chosen
Imperator was an ancient Roman title originally meaning "commander" and later associated with the supreme military and political authority of the emperor.
-
B.
Imperiale
Imperiale is a luxurious women’s watch and jewelry collection by Swiss brand Chopard, known for its elegant, regal-inspired design and refined craftsmanship.
-
C.
Emperor
The Emperor is the ceremonial monarch and symbolic head of state of Japan, representing the continuity and unity of the Japanese nation.
-
D.
Rex Romanorum
Rex Romanorum was the medieval title used for the elected ruler of the Holy Roman Empire, designating him as king of the Romans and future emperor.
-
E.
Romanus
Romanus is a Latin masculine given name and cognomen historically used throughout the Roman world and later in various European cultures.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db95c6148190bdb5f355ac04db3f |
completed | March 27, 2026, 7:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c761cfda14819088e11889f0151a37 |
completed | March 28, 2026, 5:06 a.m. |
Created at: March 27, 2026, 2:32 p.m.