Triple
T20284076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bhul-bhulaiya labyrinth |
E509827
|
entity |
| Predicate | designedPurpose |
P9494
|
FINISHED |
| Object | to confuse intruders |
—
|
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: to confuse intruders | Statement: [Bhul-bhulaiya labyrinth, designedPurpose, to confuse intruders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedPurpose Context triple: [Bhul-bhulaiya labyrinth, designedPurpose, to confuse intruders]
-
A.
designedPurposeInFiction
Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
-
B.
isDesignedFor
chosen
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
D.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
E.
purposeAndConstructionDefinedIn
Indicates that the purpose and construction details of something are specified or defined within a particular source or context.
- 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_69e0b4c652388190b782cad965e5a098 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67691516c81909f32b176edb6214c |
completed | April 20, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 10:56 a.m.