Triple
T16098557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squiggy |
E390550
|
entity |
| Predicate | typicalEntranceStyle |
P100407
|
FINISHED |
| Object | sudden door entrances |
—
|
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: sudden door entrances | Statement: [Squiggy, typicalEntranceStyle, sudden door entrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEntranceStyle Context triple: [Squiggy, typicalEntranceStyle, sudden door entrances]
-
A.
hasEntranceStyle
chosen
Indicates the architectural or design style characterizing the entrance of an entity (such as a building or space).
-
B.
entranceShape
Indicates the geometric form or outline that characterizes an entrance.
-
C.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
D.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
E.
entranceOrientation
Indicates the directional orientation or facing direction of an entrance relative to a reference frame or environment.
- 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_69d87f198bc48190a8b7e53ca15b7ead |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e1ff6672848190922b5ebb90e18947 |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e182804208819087f35307cd6e4103 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:59 a.m.