Triple
T3330285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neriglissar |
E70015
|
entity |
| Predicate | politicalStatusBeforeReign |
P47324
|
FINISHED |
| Object | high-ranking Babylonian noble |
—
|
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: high-ranking Babylonian noble | Statement: [Neriglissar, politicalStatusBeforeReign, high-ranking Babylonian noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusBeforeReign Context triple: [Neriglissar, politicalStatusBeforeReign, high-ranking Babylonian noble]
-
A.
legalStatusOfMonarch
Indicates the legal status or standing that a monarch holds within a given legal or constitutional framework.
-
B.
formerRulerState
Indicates that an entity previously held ruling authority over a given state or territory but no longer does so.
-
C.
dynasticStatus
Indicates the relationship between an entity and a ruling dynasty, such as membership in, association with, or status within that dynastic line.
-
D.
monarchyStatus
Indicates whether an entity is a monarchy and, if so, what specific monarchical status or type it holds.
-
E.
formerSovereign
Indicates that an entity once held sovereign (ruling) authority over another entity but no longer does.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb171ee0881908642504ab0ac8329 |
completed | March 8, 2026, 5:27 p.m. |
| PD | Predicate disambiguation | batch_69ada42a19348190a3862ce02451f4aa |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:12 p.m.