Triple
T28721514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooks Hatlen |
E730105
|
entity |
| Predicate | writesMessage |
P152679
|
FINISHED |
| Object | "Brooks was here" |
—
|
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: "Brooks was here" | Statement: [Brooks Hatlen, writesMessage, "Brooks was here"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesMessage Context triple: [Brooks Hatlen, writesMessage, "Brooks was here"]
-
A.
wroteMessageWith
Indicates that one entity authored or composed a message using, involving, or in association with another specified entity (such as a tool, medium, or content).
-
B.
writesSystem
Indicates that an entity authors or produces a system, such as designing, coding, or otherwise creating it.
-
C.
writingOutput
chosen
Indicates that one entity produces or generates written content as an output, typically as the result of a writing or text-creation process.
-
D.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
-
E.
writtenOut
Indicates that the content of one entity has been fully expressed, transcribed, or rendered in explicit written form as another entity.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f657099ccc8190a2b92a395f5436e7 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:53 a.m.