Triple
T31831460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laurent Brosse |
E812547
|
entity |
| Predicate | locatedInAreaOfActivity |
P111844
|
FINISHED |
| Object | Île-de-France |
E6961
|
NE 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: Île-de-France | Statement: [Laurent Brosse, locatedInAreaOfActivity, Île-de-France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInAreaOfActivity Context triple: [Laurent Brosse, locatedInAreaOfActivity, Île-de-France]
-
A.
area of activity
chosen
Indicates the domain, field, or sphere in which an entity is active or carries out its primary functions or operations.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
activeInTerritory
Indicates that an entity conducts operations, activities, or maintains a presence within a specified geographic territory.
-
D.
locatedInOrganizationally
Indicates that one entity is organizationally situated within, or belongs to, another entity in terms of administrative or structural hierarchy.
-
E.
locatedInTransportArea
Indicates that an entity is situated within a designated transport-related area or zone.
- F. None of above.
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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a01c51e2d088190b9dcce5b6de1cb9b |
completed | May 11, 2026, 12:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddc3a83c8190b4508c109947839c |
completed | June 14, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a01c4c715a48190b7435de8a9d86fd4 |
completed | May 11, 2026, noon |
Created at: April 30, 2026, 11:47 p.m.