Triple
T14918107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burgers' Rimba |
E371433
|
entity |
| Predicate | hasVisitorPath |
P116670
|
FINISHED |
| Object | walk-through trails |
—
|
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: walk-through trails | Statement: [Burgers' Rimba, hasVisitorPath, walk-through trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVisitorPath Context triple: [Burgers' Rimba, hasVisitorPath, walk-through trails]
-
A.
hasVisitorType
Indicates the type or category of visitor associated with an entity (e.g., guest, customer, tourist, patient).
-
B.
hasVisitorFunction
Indicates that an entity is associated with a function or method that implements the Visitor pattern to operate on it.
-
C.
hasVisitation
Indicates that one entity visits, or is allowed or scheduled to visit, another entity or location.
-
D.
hasVisitorBuilding
Indicates that a particular building serves as a designated visitor facility or is intended for use by visitors.
-
E.
hasVisitorPolicy
Indicates that an entity has an established policy governing the presence, behavior, or permissions of visitors.
- 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:32 a.m.