Triple
T859201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahman |
E18561
|
entity |
| Predicate | beyond |
P20249
|
FINISHED |
| Object | name and form (nama-rupa) |
—
|
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: name and form (nama-rupa) | Statement: [Brahman, beyond, name and form (nama-rupa)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beyond Context triple: [Brahman, beyond, name and form (nama-rupa)]
-
A.
above
Indicates that one entity is positioned higher than another along a vertical axis, without implying direct contact.
-
B.
near
Indicates that one entity is located at a short distance from another entity in space or position.
-
C.
bay
Indicates that one entity howls or barks loudly, often repeatedly, typically in reaction to something such as prey, the moon, or a disturbance.
-
D.
via
Indicates that something occurs, is achieved, or is connected by means of, through the use of, or along the route of another entity or medium.
-
E.
beam
Indicates that one entity emits, directs, or projects a concentrated line or stream (such as light, energy, or information) toward another entity.
- 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac50e5ec81908ac0c4b7123b4ebb |
completed | March 1, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69a4aa834a588190bca4a0eb83fb3eb6 |
completed | March 1, 2026, 9:07 p.m. |
| PDg | Predicate description generation | batch_69a4ab498bb0819080e3afb684b504b6 |
completed | March 1, 2026, 9:10 p.m. |
Created at: March 1, 2026, 7:39 p.m.