Triple
T5251166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Derby City |
E118589
|
entity |
| Predicate | hasTypeOfPlaceReferredTo |
P16688
|
FINISHED |
| Object | city |
—
|
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: city | Statement: [Derby City, hasTypeOfPlaceReferredTo, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPlaceReferredTo Context triple: [Derby City, hasTypeOfPlaceReferredTo, city]
-
A.
refersToVenueType
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
B.
refersToAdministrativeEntityType
Indicates that one entity is associated with, or designates, a specific type or category of administrative entity (such as a class of governmental or organizational unit).
-
C.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
D.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
E.
placeType
chosen
Indicates the type or category of place associated with an entity (e.g., city, park, building).
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.