Triple
T2637000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wokingham |
E59768
|
entity |
| Predicate | hasTraditionalFunction |
P32761
|
FINISHED |
| Object | market town |
—
|
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: market town | Statement: [Wokingham, hasTraditionalFunction, market town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTraditionalFunction Context triple: [Wokingham, hasTraditionalFunction, market town]
-
A.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
B.
traditionalFunction
chosen
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
-
C.
hasTraditionalSymbol
Indicates that something is associated with or represented by a conventional or culturally established symbol.
-
D.
isTraditional
Indicates that something adheres to long-established customs, practices, or norms rather than modern or innovative ones.
-
E.
hasTraditionElement
Indicates that something includes, embodies, or is associated with a particular traditional practice, custom, or cultural element.
- 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e3190081908ea828fe79569cc9 |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.