Triple
T14132242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Halles (Paris Métro) |
E350196
|
entity |
| Predicate | servesHistoricArea |
P72879
|
FINISHED |
| Object | former central market of 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: former central market of Paris | Statement: [Les Halles (Paris Métro), servesHistoricArea, former central market of Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesHistoricArea Context triple: [Les Halles (Paris Métro), servesHistoricArea, former central market of Paris]
-
A.
hasNearbyHistoricArea
chosen
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
hasHistoricDistrict
Indicates that an entity possesses or contains a designated historic district within its boundaries or domain.
-
C.
hasHistoricVillageArea
Indicates that an entity includes or is associated with an area recognized as a historic village or traditional settlement zone.
-
D.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
-
E.
historicAreaIncludes
Indicates that a designated historic area geographically contains or encompasses another place or feature within its boundaries.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610cece88190b4a86500677e5938 |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 11:24 p.m.