Triple
T3666140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moss Rock Preserve |
E77761
|
entity |
| Predicate | hasActivityLevel |
P42529
|
FINISHED |
| Object | popular local recreation area |
—
|
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: popular local recreation area | Statement: [Moss Rock Preserve, hasActivityLevel, popular local recreation area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasActivityLevel Context triple: [Moss Rock Preserve, hasActivityLevel, popular local recreation area]
-
A.
currentActivityLevel
Indicates the present intensity or degree of activity that an entity is engaged in at a given moment.
-
B.
hasActivityStatus
Indicates the current state or condition of an activity, such as whether it is planned, ongoing, completed, or cancelled.
-
C.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
-
D.
hasSignificantActivity
chosen
Indicates that an entity exhibits a notable level or intensity of activity, performance, or operation relative to a defined threshold or context.
-
E.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc40188988190b1b7ac9c8240a5ff |
completed | March 8, 2026, 6:46 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.