Triple
T19537434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fontana della Barcaccia |
E488802
|
entity |
| Predicate | hasDesignShape |
P82774
|
FINISHED |
| Object | half-sunken boat |
—
|
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: half-sunken boat | Statement: [Fontana della Barcaccia, hasDesignShape, half-sunken boat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignShape Context triple: [Fontana della Barcaccia, hasDesignShape, half-sunken boat]
-
A.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
B.
hasDistinctiveShape
chosen
Indicates that an entity possesses a shape or form that is notably different from others and can be easily recognized or distinguished.
-
C.
hasDesignOption
Indicates that an entity is associated with or offers a particular design alternative or configurable design choice.
-
D.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
-
E.
hasDesignIntent
Indicates that one entity embodies or reflects the planned purpose, function, or conceptual intent defined by 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6386fd12c81908eb5f1ef63b77156 |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
Created at: April 10, 2026, 1:41 p.m.