Triple
T24127592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue Henri-Martin |
E597847
|
entity |
| Predicate | isInDistrictKnownFor |
P120961
|
FINISHED |
| Object | affluent residential neighborhoods |
—
|
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: affluent residential neighborhoods | Statement: [Avenue Henri-Martin, isInDistrictKnownFor, affluent residential neighborhoods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInDistrictKnownFor Context triple: [Avenue Henri-Martin, isInDistrictKnownFor, affluent residential neighborhoods]
-
A.
isLocatedInDistrictKnownFor
chosen
Indicates that an entity is situated within a district that is notably recognized for a particular characteristic, feature, or reputation.
-
B.
hasFamousDistrict
Indicates that an entity possesses or contains a district that is widely recognized or renowned.
-
C.
isInTownKnownFor
Indicates that one entity is located in a town that is notable or distinguished for the other entity.
-
D.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
E.
basedInDistrict
Indicates that an entity is located or has its primary base of operations within a specific administrative district.
- 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_69e288c808b881909fed7d18f04bcbbe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df740a508190a80af01d99000127 |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:21 p.m.