Triple
T31387521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Palazzo Pucci collection |
E800636
|
entity |
| Predicate | hasMainLocationCity |
P136244
|
FINISHED |
| Object | Florence |
—
|
NE NERFINISHED |
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: Florence | Statement: [Palazzo Pucci collection, hasMainLocationCity, Florence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainLocationCity Context triple: [Palazzo Pucci collection, hasMainLocationCity, Florence]
-
A.
hasLocationCity
Indicates that an entity is situated in, occurs in, or is associated with a specific city as its location.
-
B.
hasMainPlace
Indicates that one entity is designated as the primary or central location associated with another entity.
-
C.
hasHomeCity
Indicates that an entity’s primary or official city of residence or affiliation is a specified city.
-
D.
hasMainLocationType
Indicates that an entity is associated with a primary or predominant type of location that characterizes where it is mainly situated or operates.
-
E.
primaryLocationCity
chosen
Indicates the city that serves as the main or primary location associated with the subject.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a001cc0ff588190bb7c8a6fd427d02b |
completed | May 10, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_6a001b3ea18c8190aeda7a32b2697490 |
completed | May 10, 2026, 5:44 a.m. |
Created at: April 29, 2026, 9:19 p.m.