Triple
T28631766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boxhagener Platz |
E724657
|
entity |
| Predicate | hasDayOfRegularMarket |
P98513
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [Boxhagener Platz, hasDayOfRegularMarket, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDayOfRegularMarket Context triple: [Boxhagener Platz, hasDayOfRegularMarket, Sunday]
-
A.
hasRegularMarket
Indicates that an entity maintains a recurring, scheduled marketplace or trading event where goods or services are regularly bought and sold.
-
B.
hasDailyMarket
Indicates that an entity regularly hosts or participates in a market that operates on a daily basis.
-
C.
hasTradingDays
Indicates that an entity is associated with specific days on which trading or commercial transactions are conducted.
-
D.
hasPreMarketSession
Indicates that a financial instrument or market has a designated trading session that occurs before the regular market hours.
-
E.
hasWeeklyMarket
chosen
Indicates that a place regularly hosts a market that occurs on a weekly basis.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.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 28, 2026, 4:37 a.m.