Triple
T7413599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haining |
E171071
|
entity |
| Predicate | tidalBoreSeason |
P39412
|
FINISHED |
| Object | strongest around Mid-Autumn Festival |
—
|
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: strongest around Mid-Autumn Festival | Statement: [Haining, tidalBoreSeason, strongest around Mid-Autumn Festival]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tidalBoreSeason Context triple: [Haining, tidalBoreSeason, strongest around Mid-Autumn Festival]
-
A.
hasMaximumTidalBoreHeight
Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
-
B.
tideType
Indicates the specific category or phase of the tide (such as high, low, rising, or falling) associated with a given tidal event or condition.
-
C.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
D.
seasonalFlow
chosen
Indicates that the flow or intensity of something varies in a recurring pattern according to the seasons.
-
E.
ferrySeason
Indicates that a ferry service operates or is available during a specified season or time of year.
- 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_69c68a618bdc81908d8018edadecd1a4 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2c336308190932c14cec5eec25f |
completed | March 27, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.