Triple
T21729968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tidal Wave |
E536377
|
entity |
| Predicate | queueTheming |
P88383
|
FINISHED |
| Object | flood-damaged buildings and props |
—
|
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: flood-damaged buildings and props | Statement: [Tidal Wave, queueTheming, flood-damaged buildings and props]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: queueTheming Context triple: [Tidal Wave, queueTheming, flood-damaged buildings and props]
-
A.
queueAreaTheme
chosen
Indicates the thematic style or concept applied to the area where people wait in line for an attraction or service.
-
B.
queueStyle
Indicates the manner or configuration in which items or entities are ordered and processed within a queue.
-
C.
queueType
Indicates the classification or category of a queue that specifies how items in it are organized, prioritized, or processed.
-
D.
queueTypical
Indicates that an entity is in or follows a standard or commonly expected queueing order or behavior relative to others.
-
E.
queueAreaFeature
Indicates that a feature or characteristic is associated with, or forms part of, a queue area.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd064fcc819084852b4248f65a81 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.