Triple
T26224201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brahma Ratha |
E655844
|
entity |
| Predicate | hasRope |
P168563
|
FINISHED |
| Object | specially named pulling rope |
—
|
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: specially named pulling rope | Statement: [Brahma Ratha, hasRope, specially named pulling rope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRope Context triple: [Brahma Ratha, hasRope, specially named pulling rope]
-
A.
hasRopeMaterial
Indicates that an entity is made of, or incorporates, a specified rope material.
-
B.
hasRopeWeight
Indicates that an entity is associated with a specific rope weight used for it or by it.
-
C.
usesRopes
Indicates that one entity employs or relies on ropes as tools or components in performing an action or fulfilling a function.
-
D.
hasRopeSupportStones
Indicates that a rope is used to support, hold, or suspend one or more stones.
-
E.
usedFixedRopes
Indicates that the subject relied on pre-installed fixed ropes or lines to aid in movement or support during the activity or route.
- 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 26, 2026, 8:57 p.m.