Triple
T37661504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | End Midlands |
E937726
|
entity |
| Predicate | isGeneratedAround |
P188595
|
FINISHED |
| Object | End Highlands |
—
|
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: End Highlands | Statement: [End Midlands, isGeneratedAround, End Highlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGeneratedAround Context triple: [End Midlands, isGeneratedAround, End Highlands]
-
A.
isGenerated
Indicates that one entity is produced, created, or brought into existence as a result of another entity or process.
-
B.
isGeneratedInPartBy
Indicates that something comes into existence or is produced partly as a result of another thing or process, but not solely by it.
-
C.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
-
D.
setAround
Indicates that one entity is positioned or arranged surrounding another entity or a central point.
-
E.
isPlannedAround
Indicates that one entity is organized, scheduled, or structured with consideration of, or in alignment with, another entity as a central reference or constraint.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.