Triple
T16181930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charleville |
E392702
|
entity |
| Predicate | hasMarketTraditionSince |
P8392
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Charleville, hasMarketTraditionSince, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMarketTraditionSince Context triple: [Charleville, hasMarketTraditionSince, 17th century]
-
A.
hasMarketCharterSince
Indicates that an entity has held an official market charter continuously from a specified point in time onward.
-
B.
hasTraditionIn
Indicates that a particular tradition, custom, or longstanding practice is present, observed, or established within a specified place, group, or context.
-
C.
hasHistoricMarket
Indicates that an entity possesses or is the location of a market of historical significance.
-
D.
hasMarket
Indicates that an entity possesses, operates in, or is associated with a particular market or marketplace.
-
E.
traditionSince
chosen
Indicates that a tradition has been continuously practiced or recognized 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205d858c8190802d44e08e3cdcd6 |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219d642708190ba31a90dce76a210 |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:02 a.m.