Triple
T9050441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | September 23rd Park |
E216868
|
entity |
| Predicate | hasTimeOfHighActivity |
P86087
|
FINISHED |
| Object | evening |
—
|
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: evening | Statement: [September 23rd Park, hasTimeOfHighActivity, evening]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTimeOfHighActivity Context triple: [September 23rd Park, hasTimeOfHighActivity, evening]
-
A.
hasFrequentActivity
Indicates that an entity regularly engages in or exhibits a high level of a particular activity over a given period.
-
B.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
C.
hasRecentActivity
Indicates that the subject has performed an action or been involved in an event within a defined recent time period.
-
D.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
E.
hasPopularActivity
Indicates that an entity is associated with an activity that is widely favored, frequently engaged in, or well-liked by many people.
- F. None of above. chosen
Provenance (4 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_69ca83d362e88190ae44b4e4dc194209 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc6b52cc1881909fb011d9a8af2e18 |
completed | April 1, 2026, 12:48 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee566b081909e3cdaf551dbd0ec |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f4f1cb48190a025d1b3d8d7a790 |
completed | March 31, 2026, 11:57 p.m. |
Created at: March 30, 2026, 7:10 p.m.