Triple
T30047279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arena, New York |
E763488
|
entity |
| Predicate | timeOfSubmergence |
P168388
|
FINISHED |
| Object | mid-20th century |
—
|
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: mid-20th century | Statement: [Arena, New York, timeOfSubmergence, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeOfSubmergence Context triple: [Arena, New York, timeOfSubmergence, mid-20th century]
-
A.
submergencePeriod
chosen
Indicates the duration or time interval during which something remains submerged under a liquid or water surface.
-
B.
submergedBy
Indicates that one entity is covered or overwhelmed by liquid, typically water, to the point of being beneath its surface due to the action or presence of another entity.
-
C.
timeInWater
Indicates the duration or amount of time that an entity spends in water.
-
D.
impactOfSubmergence
Indicates the effect or consequences that submerging one entity (typically in a fluid or environment) has on another entity or on its properties.
-
E.
submerged
Indicates that one entity is located beneath the surface of a liquid or other surrounding medium, typically fully covered by it.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 6:54 p.m.