Triple
T30886655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minnesota State Highway 100 |
E786784
|
entity |
| Predicate | hasLandscapingTheme |
P13651
|
FINISHED |
| Object | lilac plantings |
—
|
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: lilac plantings | Statement: [Minnesota State Highway 100, hasLandscapingTheme, lilac plantings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapingTheme Context triple: [Minnesota State Highway 100, hasLandscapingTheme, lilac plantings]
-
A.
hasLandscaping
chosen
Indicates that an entity possesses or is associated with designed outdoor grounds or landscape features.
-
B.
hasGardenType
Indicates that an entity possesses or is associated with a garden of a specified type.
-
C.
hasLandscapeDesignInfluence
Indicates that one entity has influenced or shaped the landscape design style, principles, or features of another entity.
-
D.
hasGardenUse
Indicates that something is used for, or serves a particular function within, a garden.
-
E.
hasLandscapeArchitecturalStyle
Indicates that something (such as a site or landscape) is designed or characterized according to a particular landscape architectural style.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
Created at: April 29, 2026, 8:49 p.m.