Triple
T36885112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grammichele |
E911587
|
entity |
| Predicate | hasStreetPlanShape |
P47409
|
FINISHED |
| Object | hexagonal |
—
|
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: hexagonal | Statement: [Grammichele, hasStreetPlanShape, hexagonal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreetPlanShape Context triple: [Grammichele, hasStreetPlanShape, hexagonal]
-
A.
hasStreetPlan
chosen
Indicates that an entity possesses or is associated with a specific layout or design plan for its streets.
-
B.
hasCityPlanShape
Indicates that an entity’s overall city layout or urban plan conforms to a particular geometric or structural shape.
-
C.
streetPlanBy
Indicates that a street or road layout was designed, organized, or planned by a particular agent or authority.
-
D.
hasFloorPlanShape
Indicates that an entity has a specific geometric or structural configuration defining the shape of its floor plan.
-
E.
hasStreetPatternRelation
Indicates a relationship between two areas or locations based on the similarity, alignment, or structural correspondence of their street patterns.
- 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_69f76e8335908190b77e7e11d0e80820 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a005d878aec81908e1177914a8fb610 |
completed | May 10, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_6a005c382f8881908ff33ebb7f88c430 |
completed | May 10, 2026, 10:21 a.m. |
Created at: May 3, 2026, 4:13 p.m.