Triple
T4309617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book of 2 Kings |
E94038
|
entity |
| Predicate | recordsEvent |
P9348
|
FINISHED |
| Object | fall of Samaria |
—
|
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: fall of Samaria | Statement: [Book of 2 Kings, recordsEvent, fall of Samaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordsEvent Context triple: [Book of 2 Kings, recordsEvent, fall of Samaria]
-
A.
recordHeld
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
B.
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).
-
C.
recordAttendance
Indicates that an entity documents or logs the presence or participation of another entity at a specific event, session, or time.
-
D.
recorded
chosen
Indicates that one entity captured, stored, or documented information, audio, video, or data about another entity or event.
-
E.
recordSettingVenueFor
Indicates the venue or location where a particular record (such as a performance, achievement, or measurement) was 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d40748819084798058396be113 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:11 p.m.