Triple
T16638792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonsecours Market |
E404275
|
entity |
| Predicate | marketUseEnd |
P123682
|
FINISHED |
| Object | 1963 |
—
|
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: 1963 | Statement: [Bonsecours Market, marketUseEnd, 1963]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketUseEnd Context triple: [Bonsecours Market, marketUseEnd, 1963]
-
A.
marketUse
Indicates that something is used, applied, or exploited within a market or commercial context.
-
B.
endMarket
Indicates the market or customer segment where a product, service, or output is ultimately sold or used.
-
C.
industrialUseEnd
Indicates the point in time or condition at which an industrial use or application of something is terminated or ceases.
-
D.
marketExit
Indicates that an entity ceases operating, selling, or competing in a particular market or geographic/segment context.
-
E.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
- F. None of above. chosen
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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37acff38081908c8044936b794ce0 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e296ad3f148190af09223dc35b155c |
completed | April 17, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69e2d7fb02f481908885a226c2191231 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:18 a.m.