Triple
T15958865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agatha |
E387005
|
entity |
| Predicate | usedBySystemFor |
P98
|
FINISHED |
| Object | predicting future murders |
—
|
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: predicting future murders | Statement: [Agatha, usedBySystemFor, predicting future murders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBySystemFor Context triple: [Agatha, usedBySystemFor, predicting future murders]
-
A.
usedBySystem
Indicates that something is utilized or operated by a particular system.
-
B.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
-
C.
usedByProgram
Indicates that a particular resource, component, or element is utilized or consumed by a specific program.
-
D.
usedByServer
Indicates that something (such as a resource, component, or configuration) is utilized or relied upon by a server in its operation.
-
E.
usedInternally
Indicates that something is utilized within an organization, system, or component itself rather than being exposed or provided for external use.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.