Triple
T30102861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thames Head pub |
E765045
|
entity |
| Predicate | typicalClienteleActivity |
P1164
|
FINISHED |
| Object | walking |
—
|
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: walking | Statement: [Thames Head pub, typicalClienteleActivity, walking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClienteleActivity Context triple: [Thames Head pub, typicalClienteleActivity, walking]
-
A.
typicalActivity
chosen
Indicates that an entity is commonly or characteristically engaged in a particular activity.
-
B.
typicalInteraction
Indicates the usual or most common way in which two entities interact or relate to each other.
-
C.
typicalVisitType
Indicates the usual or most common category of visit associated with an entity or event.
-
D.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
typicalGroup
Indicates that the subject belongs to or represents a standard, characteristic, or commonly occurring group associated with the object.
- 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_69f22474e4288190b5f895fe3974aa92 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a036c1282748190a820562bcd9aa5d9 |
completed | May 12, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_6a036bb5ca0c8190bd50abc197960b41 |
completed | May 12, 2026, 6:04 p.m. |
Created at: April 29, 2026, 7:08 p.m.