Triple
T19381722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonadab |
E484826
|
entity |
| Predicate | knewAbout |
P22660
|
FINISHED |
| Object | Absalom’s plan to kill Amnon |
—
|
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: Absalom’s plan to kill Amnon | Statement: [Jonadab, knewAbout, Absalom’s plan to kill Amnon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knewAbout Context triple: [Jonadab, knewAbout, Absalom’s plan to kill Amnon]
-
A.
knows
chosen
Indicates that one entity has knowledge or awareness of another entity or piece of information.
-
B.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
C.
knownBefore
Indicates that one entity had knowledge or awareness of another entity or event prior to a specified time or before another referenced event occurred.
-
D.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
E.
известноКак
Indicates that one entity is known or referred to by another name, designation, or alias.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a6075a88190aed7afa3b8fd3021 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.