Triple
T38244206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Park perimeter |
E1013849
|
entity |
| Predicate | hasTypicalActivityLevel |
P120176
|
FINISHED |
| Object | heavily used on weekends |
—
|
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: heavily used on weekends | Statement: [Central Park perimeter, hasTypicalActivityLevel, heavily used on weekends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalActivityLevel Context triple: [Central Park perimeter, hasTypicalActivityLevel, heavily used on weekends]
-
A.
humanActivityLevel
Indicates the degree or intensity of activity or movement performed by a human over a given period or in a given context.
-
B.
typicalActivityLevel
chosen
Indicates the usual intensity or amount of activity that an entity engages in under normal conditions.
-
C.
dayActivityLevel
Indicates the overall intensity or amount of activity performed during a given day.
-
D.
currentActivityLevel
Indicates the present intensity or degree of activity that an entity is engaged in at a given moment.
-
E.
primaryLevelOfActivity
Indicates the main or most significant level at which an entity engages in a particular activity or operation.
- 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0010e46d948190a51111b5270fade7 |
completed | May 10, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_6a001061d34c8190bfe73f3d7c061eb7 |
completed | May 10, 2026, 4:58 a.m. |
Created at: May 3, 2026, 4:30 p.m.