Triple
T36390684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mill House |
E896317
|
entity |
| Predicate | geographicScopeOfCareer |
P192254
|
FINISHED |
| Object | Great Britain |
—
|
NE NERFINISHED |
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: Great Britain | Statement: [Mill House, geographicScopeOfCareer, Great Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicScopeOfCareer Context triple: [Mill House, geographicScopeOfCareer, Great Britain]
-
A.
geographicScopeDiscussed
Indicates that the discussion or content addresses, covers, or pertains to a particular geographic area or region.
-
B.
geographicScopeClaimed
Indicates the geographic area or territory that an entity asserts or claims as being within its scope, authority, or coverage.
-
C.
geographicAreaOfSupport
Indicates the geographic region or area within which support, assistance, or services are provided or applicable.
-
D.
geographicCoverageType
Indicates the type or nature of the geographic area that something covers or applies to.
-
E.
jurisdictionOfEmployment
Indicates the legal or geographic jurisdiction under whose laws or authority an employment relationship is established or governed.
- F. None of above. chosen
Provenance (4 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
| PDg | Predicate description generation | batch_69fd026757a081909911a59a78652709 |
completed | May 7, 2026, 9:21 p.m. |
Created at: May 3, 2026, 4:10 p.m.