Triple
T38626061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cité Florale |
E937012
|
entity |
| Predicate | streetNamesTheme |
P36245
|
FINISHED |
| Object | flower names |
—
|
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: flower names | Statement: [Cité Florale, streetNamesTheme, flower names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streetNamesTheme Context triple: [Cité Florale, streetNamesTheme, flower names]
-
A.
streetPatternNamedFor
Indicates that a street pattern or layout is named in honor of, or derived from, a particular entity.
-
B.
streetSet
Indicates that a particular street belongs to, or is included within, a specified set or collection of streets.
-
C.
hasStreetNamingPattern
chosen
Indicates that there is a characteristic or systematic way in which streets are named in relation to a given entity.
-
D.
inUniverseStreetName
Indicates that a street has a specific name within the context of a particular fictional or defined universe.
-
E.
cityStreetUsed
Indicates that a particular city street is utilized or traversed in the course of some activity, route, or event.
- 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_69f76ed403208190b862dc795171353f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.