Triple
T5074826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grihyasutras |
E114367
|
entity |
| Predicate | laterWrittenDown |
P36227
|
FINISHED |
| Object | manuscript form |
—
|
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: manuscript form | Statement: [Grihyasutras, laterWrittenDown, manuscript form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterWrittenDown Context triple: [Grihyasutras, laterWrittenDown, manuscript form]
-
A.
laterWrittenDownIn
chosen
Indicates that information, events, or content were recorded or documented at a later time than when they originally occurred or were created.
-
B.
laterWrittenDownAs
Indicates that something was recorded or documented in written form at a subsequent time after its original occurrence or expression.
-
C.
laterWrittenIn
Indicates that one text or version was written at a later time than another, establishing a chronological order between the writings.
-
D.
likelyWrittenFrom
Indicates that something (such as a text, statement, or perspective) is probably authored or expressed from the viewpoint, context, or position of a particular entity.
-
E.
writtenTo
Indicates that something has been addressed or directed in written form to a particular recipient.
- 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_69bd443cf28c8190ad371d603563dbdd |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.