Triple
T22506909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | inscription of Nebuchadnezzar II |
E556412
|
entity |
| Predicate | mentionsTitleOf |
P3254
|
FINISHED |
| Object | king of Babylon |
—
|
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: king of Babylon | Statement: [inscription of Nebuchadnezzar II, mentionsTitleOf, king of Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mentionsTitleOf Context triple: [inscription of Nebuchadnezzar II, mentionsTitleOf, king of Babylon]
-
A.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
B.
usesTitleIn
Indicates that an entity is referred to using a particular title within a specified context or medium.
-
C.
containsTitle
chosen
Indicates that one entity includes or holds another entity’s title as part of its content or metadata.
-
D.
hasTitleOf
Indicates that one entity holds, bears, or is designated by the official title, name, or rank specified by another entity.
-
E.
associatedTitle
Indicates that one entity has a title, designation, or formal label that is linked or relevant to another entity.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5cddf88190821d9c9fdee84160 |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.