Triple
T34640158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elvenking's Halls |
E889532
|
entity |
| Predicate | guardedEntrance |
P46861
|
FINISHED |
| Object | stone bridge |
—
|
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 bridge | Statement: [Elvenking's Halls, guardedEntrance, stone bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guardedEntrance Context triple: [Elvenking's Halls, guardedEntrance, stone bridge]
-
A.
guardedEntranceTo
chosen
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
B.
guardedPassage
Indicates that access through a passage is controlled or protected by a guard or security presence.
-
C.
guardedIn
Indicates that one entity is protected or kept under watch within the bounds or premises of another entity.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
guardedSectionOf
Indicates a relationship where one entity serves as a protective or security boundary for a specific section or portion of another entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f72291022081909c00d6aec5098b50 |
completed | May 3, 2026, 10:25 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:04 a.m.