Triple
T31915520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Town of Paris |
E814815
|
entity |
| Predicate | hasQuietResidentialAreas |
P172726
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Town of Paris, hasQuietResidentialAreas, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasQuietResidentialAreas Context triple: [Town of Paris, hasQuietResidentialAreas, true]
-
A.
hasResidentialArea
Indicates that an entity includes, contains, or is associated with an area designated for people to live or reside.
-
B.
isInResidentialArea
Indicates that something is located within a residential area, such as a neighborhood or zone primarily designated for housing.
-
C.
isSuburbanResidentialArea
Indicates that a location is primarily a residential neighborhood situated in a suburban (non-urban, non-rural) setting.
-
D.
hasDevelopingResidentialZones
Indicates that an area or region contains residential zones that are currently under development or in the process of being built.
-
E.
hasNoCommercialZone
Indicates that the subject area or entity does not contain any designated commercial zone or commercial-use area.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1eceb6c8190bc7775c0fe4c26eb |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: May 1, 2026, 12:02 a.m.