Triple
T36270378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinhoyi Caves Motel |
E892652
|
entity |
| Predicate | typicalGuestActivity |
P1164
|
FINISHED |
| Object | visiting Chinhoyi Caves |
—
|
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: visiting Chinhoyi Caves | Statement: [Chinhoyi Caves Motel, typicalGuestActivity, visiting Chinhoyi Caves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGuestActivity Context triple: [Chinhoyi Caves Motel, typicalGuestActivity, visiting Chinhoyi Caves]
-
A.
typicalGuests
Indicates the usual or most common guests associated with a particular host, place, or event.
-
B.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
C.
contestantActivity
Indicates that a contestant engages in or performs a particular activity within a competition or contest context.
-
D.
typicalGuestConfederation
Indicates that one entity is typically a guest or participant within the confederation represented by the other entity.
-
E.
hostsActivitiesOf
Indicates that one entity provides the venue, context, or platform in which the activities of another entity take place.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.