Triple
T652133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cyrus Cylinder |
E11366
|
entity |
| Predicate | content |
P4446
|
FINISHED |
| Object | proclamation of Cyrus as 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: proclamation of Cyrus as king of Babylon | Statement: [Cyrus Cylinder, content, proclamation of Cyrus as king of Babylon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: content Context triple: [Cyrus Cylinder, content, proclamation of Cyrus as king of Babylon]
-
A.
article2Content
Indicates that one article serves as the content or body text for another article or higher-level publication entity.
-
B.
primaryContent
chosen
Indicates that one entity serves as the main or most important content associated with another entity.
-
C.
GCContent
Indicates the proportion of guanine (G) and cytosine (C) bases relative to the total nucleotide content in a DNA or RNA sequence.
-
D.
context
Indicates that one entity provides the surrounding circumstances, setting, or background within which another entity, event, or statement occurs or is interpreted.
-
E.
body
Indicates that one entity is the physical body or main corporeal form of 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f35acb08190a3a8248023ce07f9 |
completed | March 1, 2026, 8:19 p.m. |
| PD | Predicate disambiguation | batch_69a49d1001088190aa7ca3c8f2ad0e32 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.