Triple
T32471701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toghrol Tower |
E829863
|
entity |
| Predicate | hasExteriorForm |
P123659
|
FINISHED |
| Object | polygonal outer surface |
—
|
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: polygonal outer surface | Statement: [Toghrol Tower, hasExteriorForm, polygonal outer surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExteriorForm Context triple: [Toghrol Tower, hasExteriorForm, polygonal outer surface]
-
A.
hasExteriorType
Indicates that an entity possesses a specific kind or style of exterior.
-
B.
hasExteriorStyle
Indicates that an entity possesses or is characterized by a particular exterior design or stylistic appearance.
-
C.
exteriorShape
chosen
Indicates the overall outer form or contour that characterizes how something appears from the outside.
-
D.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
E.
exteriorBasedOn
Indicates that the exterior of one entity is designed, derived, or determined based on the characteristics or specifications of another entity.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 12:57 a.m.