Triple
T28106581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | People's Park (Shanghai) |
E710379
|
entity |
| Predicate | hasWeekendEvent |
P85404
|
FINISHED |
| Object | marriage market |
—
|
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: marriage market | Statement: [People's Park (Shanghai), hasWeekendEvent, marriage market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeekendEvent Context triple: [People's Park (Shanghai), hasWeekendEvent, marriage market]
-
A.
hasRecreationEvent
Indicates that an entity is associated with, organizes, or participates in a recreational event or activity.
-
B.
weekendEvent
chosen
Indicates that an event occurs during the weekend period (typically Saturday and/or Sunday).
-
C.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
-
D.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
E.
hasDailyEvent
Indicates that an entity is associated with an event that occurs every day.
- 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_69ef9b71fdb081908b4a61cd7ff147c1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6645ba71c81908044ade6ab577018 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 9:08 p.m.