Triple
T8303658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Église Saint-Vincent-de-Paul |
E194405
|
entity |
| Predicate | isInUrbanContext |
P82630
|
FINISHED |
| Object | central Paris |
—
|
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: central Paris | Statement: [Église Saint-Vincent-de-Paul, isInUrbanContext, central Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInUrbanContext Context triple: [Église Saint-Vincent-de-Paul, isInUrbanContext, central Paris]
-
A.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
B.
appliesToUrbanArea
Indicates that the relationship, rule, or condition is specifically relevant or applicable to an urban area.
-
C.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
-
D.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
E.
isUrbanForm
Indicates that an entity represents or exhibits characteristics of an urban built environment or city-like spatial structure.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8b9f6081909100d1da8a078616 |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d648988190ab0669cc0592e827 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:53 p.m.