Triple
T20223834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenclaw Tower |
E495324
|
entity |
| Predicate | doorGuardedBy |
P95055
|
FINISHED |
| Object | bronze eagle-shaped knocker |
—
|
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: bronze eagle-shaped knocker | Statement: [Ravenclaw Tower, doorGuardedBy, bronze eagle-shaped knocker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doorGuardedBy Context triple: [Ravenclaw Tower, doorGuardedBy, bronze eagle-shaped knocker]
-
A.
hasDoorGuard
chosen
Indicates that an entity has another entity serving as a guard for its door or entrance.
-
B.
residenceGuarded
Indicates that a residence is being actively protected or watched over, typically for security purposes.
-
C.
doorSafety
Indicates that a door meets specified safety conditions or standards, such as being secure, unobstructed, and compliant with safety regulations.
-
D.
doorSymbol
Indicates a symbolic representation that denotes or marks the presence or concept of a door.
-
E.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.