Triple
T37974349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finding Everett Ruess |
E947379
|
entity |
| Predicate | usesWritingsOf |
P189687
|
FINISHED |
| Object | Everett Ruess |
—
|
NE NERFINISHED |
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: Everett Ruess | Statement: [Finding Everett Ruess, usesWritingsOf, Everett Ruess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWritingsOf Context triple: [Finding Everett Ruess, usesWritingsOf, Everett Ruess]
-
A.
usedInWritingFor
Indicates that something (e.g., a tool, material, or medium) is employed as part of the process or context of writing for a particular purpose or audience.
-
B.
usedInWriting
Indicates that something (such as a tool, material, or medium) is employed as part of the process or act of writing.
-
C.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
writtenAgainst
Indicates that a written work (such as a document, article, or statement) is composed in opposition to, or as a critique or complaint about, a particular target.
- F. None of above. chosen
Provenance (4 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_69f76ef7db908190bba6086673a32300 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc7b6c2c88190ad4f58980834053c |
completed | May 6, 2026, 10:59 p.m. |
Created at: May 3, 2026, 4:20 p.m.