Triple
T29055266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Musasir |
E735367
|
entity |
| Predicate | sackRecordedIn |
P41398
|
FINISHED |
| Object | Sargon II’s campaign annals |
—
|
NE NERFINISHED |
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: Sargon II’s campaign annals | Statement: [Musasir, sackRecordedIn, Sargon II’s campaign annals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sackRecordedIn Context triple: [Musasir, sackRecordedIn, Sargon II’s campaign annals]
-
A.
recorded
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
B.
recordHeldIn
chosen
Indicates that a record is stored, maintained, or kept within a particular location, system, or repository.
-
C.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
D.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
E.
areRecordedBy
Indicates that an event, observation, or piece of information is captured or documented by a specific recording agent, device, or process.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f66091e30081908396b27a885d36b1 |
completed | May 2, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:11 a.m.