Triple
T6057075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piazza del Campidoglio |
E134939
|
entity |
| Predicate | hasPavingDesign |
P58826
|
FINISHED |
| Object | oval star-shaped pattern |
—
|
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: oval star-shaped pattern | Statement: [Piazza del Campidoglio, hasPavingDesign, oval star-shaped pattern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPavingDesign Context triple: [Piazza del Campidoglio, hasPavingDesign, oval star-shaped pattern]
-
A.
hasPavementPattern
chosen
Indicates that an entity possesses or is characterized by a specific pattern or design in its pavement surface.
-
B.
pavedWith
Indicates that a surface or area is covered or constructed using a specified material as its paving.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
roofPatternInspiredBy
Indicates that the design or arrangement of a roof follows or is derived from a particular pattern, style, or source of inspiration.
-
E.
hasStepDesign
Indicates that one entity possesses or incorporates a particular step-related design or configuration in relation to 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570bf01c8190a8b2c25b7805d403 |
completed | March 22, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69c049edc6f0819092ca620d9073ad26 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:09 p.m.