Triple
T7715686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steeple Bumpleigh |
E174873
|
entity |
| Predicate | hasWorkLocationType |
P28105
|
FINISHED |
| Object | rural village |
—
|
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: rural village | Statement: [Steeple Bumpleigh, hasWorkLocationType, rural village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorkLocationType Context triple: [Steeple Bumpleigh, hasWorkLocationType, rural village]
-
A.
hasWorkforceType
Indicates the type or category of workforce associated with an entity (such as permanent, temporary, contract, or part-time).
-
B.
hasMainLocationType
chosen
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
C.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
D.
hasWorkStyle
Indicates the type or manner in which an entity typically performs work or carries out tasks.
-
E.
hasWorksLocatedIn
Indicates that the works or creations associated with an entity are situated or stored in a specified location.
- 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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.