Triple
T29211890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budhan |
E740566
|
entity |
| Predicate | associatedWithWriting |
P153734
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Budhan, associatedWithWriting, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWriting Context triple: [Budhan, associatedWithWriting, true]
-
A.
hasWritingAssociated
chosen
Indicates that there is a piece of writing (such as a text, document, or inscription) linked or connected to the given entity.
-
B.
usesWritingsOf
Indicates that one entity makes use of, relies on, or draws from the writings or written works produced by another entity.
-
C.
usesWriting
Indicates that one entity employs or applies a particular writing system, script, or written form for communication or representation.
-
D.
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.
-
E.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a0324c2d618819093f7e6424b0f5baf |
completed | May 12, 2026, 1:01 p.m. |
| PD | Predicate disambiguation | batch_6a0324292e588190b37d0c3016ea2062 |
completed | May 12, 2026, 12:59 p.m. |
Created at: April 28, 2026, 12:11 p.m.