Triple
T944737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feuillants |
E20386
|
entity |
| Predicate | usedAsMeetingPlace |
P16368
|
FINISHED |
| Object | former Feuillant monastery in 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 Feuillant monastery in Paris | Statement: [Feuillants, usedAsMeetingPlace, former Feuillant monastery in Paris]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsMeetingPlace Context triple: [Feuillants, usedAsMeetingPlace, former Feuillant monastery in Paris]
-
A.
traditionalMeetingPlace
Indicates that a location is customarily used as a gathering spot for meetings or social interactions according to established tradition.
-
B.
previousMeetingPlace
Indicates the location where two or more entities met on a prior occasion.
-
C.
meetsInPlaceOf
Indicates that one entity meets or comes together with another specifically at a designated place or location.
-
D.
gatheringPlace
chosen
Indicates a location where entities come together or assemble, typically for a shared activity, purpose, or event.
-
E.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a3ed3881908386af140477c514 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.