Triple
T944275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shirley |
E20376
|
entity |
| Predicate | originallyReferredTo |
P13656
|
FINISHED |
| Object | a place name in England |
—
|
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: a place name in England | Statement: [Shirley, originallyReferredTo, a place name in England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyReferredTo Context triple: [Shirley, originallyReferredTo, a place name in England]
-
A.
originallyOpenedBy
Indicates that an entity was first opened, launched, or made operational by a specific agent or organization.
-
B.
originallyIn
chosen
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
-
C.
originallyEnforcedBy
Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
-
D.
originallyMaintainedBy
Indicates that an entity was first managed, supported, or kept in working order by a particular agent or organization, regardless of who maintains it later.
-
E.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular entity.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a3ed3881908386af140477c514 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.