Triple
T556854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hay |
E11959
|
entity |
| Predicate | isServiceCentreFor |
P16350
|
FINISHED |
| Object | surrounding pastoral district |
—
|
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: surrounding pastoral district | Statement: [Hay, isServiceCentreFor, surrounding pastoral district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isServiceCentreFor Context triple: [Hay, isServiceCentreFor, surrounding pastoral district]
-
A.
serviceOf
Indicates that one entity performs, provides, or fulfills a function or duty on behalf of another entity.
-
B.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
C.
isServedAt
Indicates that something (such as food, drink, or a service) is provided or made available at a particular place or venue.
-
D.
mobilizationCentre
Indicates a location where resources, personnel, or equipment are gathered and organized in preparation for deployment or coordinated action.
-
E.
serviceNumber
Indicates a unique identifying number assigned to a service, used to reference, track, or distinguish that service from others.
- 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_69a4932941d08190815efd422f0b4ca7 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4991ef9b0819092ec0407270373f4 |
completed | March 1, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69a494bd78e8819083c519669158f209 |
completed | March 1, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69a4985952a481908b918350ececf484 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:32 p.m.