Triple
T23968886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark Sway |
E604170
|
entity |
| Predicate | knowsInformationAbout |
P22660
|
FINISHED |
| Object | location of Senator Boyd Boyette’s body |
—
|
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: location of Senator Boyd Boyette’s body | Statement: [Mark Sway, knowsInformationAbout, location of Senator Boyd Boyette’s body]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knowsInformationAbout Context triple: [Mark Sway, knowsInformationAbout, location of Senator Boyd Boyette’s body]
-
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.
organFamousFor
Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
-
D.
referentKnownFor
Indicates that the referent is widely recognized or notable for a particular activity, role, achievement, or characteristic.
-
E.
providesInformationIn
Indicates that one entity supplies or conveys information within or through another entity or context.
- 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1da2ab08190bfe653fb5a9f2c96 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:25 p.m.