Triple
T36450078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial District |
E897982
|
entity |
| Predicate | hasTypicalActivityPattern |
P86087
|
FINISHED |
| Object | weekday daytime peak |
—
|
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: weekday daytime peak | Statement: [Financial District, hasTypicalActivityPattern, weekday daytime peak]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalActivityPattern Context triple: [Financial District, hasTypicalActivityPattern, weekday daytime peak]
-
A.
hasFrequentActivity
Indicates that an entity regularly engages in or exhibits a high level of a particular activity over a given period.
-
B.
hasTimeOfHighActivity
chosen
Indicates that an entity experiences its peak or most intense level of activity during a specified time period.
-
C.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
D.
hasHumanActivities
Indicates that certain human actions, behaviors, or practices are present, performed, or associated with a given entity.
-
E.
hasSignificantActivity
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
- 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_69f76e5720b481908f8177ac24a7560b |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff9a25407c81909faa86e72a7a9d17 |
completed | May 9, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69ff99c613688190a03b2f93d5ccad2b |
completed | May 9, 2026, 8:32 p.m. |
Created at: May 3, 2026, 4:10 p.m.