Triple
T9386026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Terror |
E225906
|
entity |
| Predicate | hasPanelLayout |
P17102
|
FINISHED |
| Object | dynamic action-oriented |
—
|
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: dynamic action-oriented | Statement: [Holy Terror, hasPanelLayout, dynamic action-oriented]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPanelLayout Context triple: [Holy Terror, hasPanelLayout, dynamic action-oriented]
-
A.
hasPanel
Indicates that one entity includes, is equipped with, or is associated with a panel as a component or feature.
-
B.
hasPanelFormat
chosen
Indicates that something is associated with a particular panel layout or format used for its presentation or display.
-
C.
hasPanelComposition
Indicates that something is composed of or structured into multiple panels or panel-like sections.
-
D.
hasLayout
Indicates that one entity defines or is associated with the structural arrangement or organization (layout) of another entity.
-
E.
hasNumberOfInscribedPanels
Indicates the relationship that specifies how many inscribed panels are associated with a given 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d3964c8190b0353f56df755db8 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:44 p.m.