Triple
T14491127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garbhagriha |
E359363
|
entity |
| Predicate | isUsuallyBuiltWith |
P11047
|
FINISHED |
| Object | stone |
—
|
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: stone | Statement: [Garbhagriha, isUsuallyBuiltWith, stone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUsuallyBuiltWith Context triple: [Garbhagriha, isUsuallyBuiltWith, stone]
-
A.
isBuiltFor
Indicates that one entity is specifically designed, intended, or optimized to serve, support, or accommodate another entity or purpose.
-
B.
builtOn
Indicates that one entity is constructed, developed, or established using another entity as its base, foundation, or underlying platform.
-
C.
builtWithAssistanceFrom
Indicates that something was constructed, created, or developed with help, support, or collaboration from another party.
-
D.
builtFrom
chosen
Indicates that one entity is constructed, composed, or formed using another entity as its material, component, or source.
-
E.
builtWithout
Indicates that something was constructed or created in the absence of a particular component, material, tool, or condition.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930d820481908b9813014dd02540 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.