Triple
T14021247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Insurance City |
E337334
|
entity |
| Predicate | hasTypeOfPlaceReferred |
P10640
|
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: [The Insurance City, hasTypeOfPlaceReferred, city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPlaceReferred Context triple: [The Insurance City, hasTypeOfPlaceReferred, city]
-
A.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
B.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
C.
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).
-
D.
refersToCityOn
Indicates that one entity makes reference to, or is specifically about, a particular city located on a given date or temporal context.
-
E.
isDerivedFromPlace
Indicates that something originates, is obtained, or conceptually comes from a particular place or location.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f3c7cd88190b236382058581740 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:19 p.m.