Triple
T15535558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pipe Plaza |
E370329
|
entity |
| Predicate | hasShortcutType |
P118542
|
FINISHED |
| Object | pipe shortcuts |
—
|
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: pipe shortcuts | Statement: [Pipe Plaza, hasShortcutType, pipe shortcuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasShortcutType Context triple: [Pipe Plaza, hasShortcutType, pipe shortcuts]
-
A.
hasShortcut
Indicates that one entity serves as a shortcut or quick-access link to another entity.
-
B.
hasShortcuts
chosen
Indicates that an entity provides or supports shortcut actions or quick-access commands to perform operations more efficiently.
-
C.
hasShortFormRelationType
Indicates that one entity serves as an abbreviated, shortened, or acronym form of another entity.
-
D.
hasShort
Indicates that an entity possesses or is characterized by something of short length or duration.
-
E.
hasShortcutGlitches
Indicates that the subject exhibits malfunctions or irregular behavior specifically related to its shortcut functionality.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.