Triple
T15770538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porte de la Roseraie entrance |
E382341
|
entity |
| Predicate | isAccessPointOf |
P120267
|
FINISHED |
| Object | urban park |
—
|
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: urban park | Statement: [Porte de la Roseraie entrance, isAccessPointOf, urban park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAccessPointOf Context triple: [Porte de la Roseraie entrance, isAccessPointOf, urban park]
-
A.
hasAccessPointFrom
Indicates that an entity can be reached or entered from a specific access point.
-
B.
isMajorAccessPointFor
Indicates that something serves as a primary or significant entry or connection point for accessing another entity or system.
-
C.
modernAccessPoint
Indicates that an entity serves as a contemporary or up-to-date point of entry, connection, or interaction for accessing another entity or resource.
-
D.
isHotspotTrackOf
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
E.
isStartingPointOf
Indicates that something serves as the initial point or origin from which another thing, process, or path begins.
- F. None of above. chosen
Provenance (4 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_69d86da09a10819082fe9797b23e4664 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e051962fe08190a6201dd48196a9ee |
completed | April 16, 2026, 3:03 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e03cc871d0819085c0fc54de7984ff |
completed | April 16, 2026, 1:35 a.m. |
Created at: April 10, 2026, 4:47 a.m.