Triple
T27514367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Microcentro |
E694502
|
entity |
| Predicate | hasDailyActivityPattern |
P86087
|
FINISHED |
| Object | peak activity on weekdays |
—
|
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: peak activity on weekdays | Statement: [Microcentro, hasDailyActivityPattern, peak activity on weekdays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDailyActivityPattern Context triple: [Microcentro, hasDailyActivityPattern, peak activity on weekdays]
-
A.
hasFrequentActivity
Indicates that an entity regularly engages in or exhibits a high level of a particular activity over a given period.
-
B.
hasDailyUse
Indicates that something is used or occurs on a daily, regular basis.
-
C.
hasDailyEvent
Indicates that an entity is associated with an event that occurs every day.
-
D.
hasTimeOfHighActivity
chosen
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
E.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
- 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_69ef53842afc8190ba6bd4e4999bda67 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 1:18 p.m.