Triple
T32658132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Obelisk of Shalmaneser III |
E834919
|
entity |
| Predicate | hasNumberOfRegisters |
P112754
|
FINISHED |
| Object | five per side |
—
|
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: five per side | Statement: [Black Obelisk of Shalmaneser III, hasNumberOfRegisters, five per side]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfRegisters Context triple: [Black Obelisk of Shalmaneser III, hasNumberOfRegisters, five per side]
-
A.
numberOfRegisters
chosen
Indicates the total count of registers associated with or contained in a given entity.
-
B.
numberOfRegistersInitial
Indicates the initial count of registers associated with an entity at the start of a process or configuration.
-
C.
numberOfGeneralPurposeRegisters
Indicates the quantity of general-purpose registers associated with or available in a given computing context.
-
D.
segmentRegisterCount
Indicates the number of register units associated with or allocated to a particular segment in a system or structure.
-
E.
numberOfIndexRegisters
Indicates the quantity of index registers associated with or available to a given entity (such as a processor or instruction set).
- 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe2f078c24819082ba396b56f02808 |
completed | May 8, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69fe228fe1988190baf3bb34897f3dbe |
completed | May 8, 2026, 5:51 p.m. |
Created at: May 1, 2026, 1:08 a.m.