Triple
T16561200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pincio |
E402341
|
entity |
| Predicate | developedAsGardenIn |
P43650
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Pincio, developedAsGardenIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsGardenIn Context triple: [Pincio, developedAsGardenIn, 19th century]
-
A.
createdAsGarden
chosen
Indicates that something was brought into existence or established specifically in the form or function of a garden.
-
B.
containsGarden
Indicates that one entity includes or has a garden within its area or boundaries.
-
C.
gardensBuiltFor
Indicates that one entity (such as a garden or landscaped area) was created or designed specifically for the benefit, use, or purpose of another entity.
-
D.
gardenValue
Indicates that one entity assigns or possesses a particular value, worth, or importance in relation to a garden.
-
E.
developedAlong
Indicates that something was created, constructed, or evolved following the course, path, or boundary of something else.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3576d88288190b33543bea4706a36 |
completed | April 18, 2026, 10:05 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.