Triple
T6874115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Touquet-Paris-Plage |
E158628
|
entity |
| Predicate | addedSuffixFor |
P42400
|
FINISHED |
| Object | attracting Parisians |
—
|
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: attracting Parisians | Statement: [Le Touquet-Paris-Plage, addedSuffixFor, attracting Parisians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedSuffixFor Context triple: [Le Touquet-Paris-Plage, addedSuffixFor, attracting Parisians]
-
A.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
B.
usedAsSuffixTo
chosen
Indicates that one entity functions as a suffix appended to another entity, typically to modify or extend its meaning.
-
C.
hasNameSuffix
Indicates that an entity’s name includes a specific suffix or ending component.
-
D.
registrationSuffix
Indicates the trailing part or extension added to a base registration identifier to form a complete registration code.
-
E.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
- 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_69c68832af1481908ce356e133ebaebe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d8c8d3888190b1c1f74aa66d6071 |
completed | March 27, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b363dc8190a7225b540ab2bc40 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:22 p.m.