Triple
T9290967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambrésis |
E223513
|
entity |
| Predicate | currentUseOfName |
P13305
|
FINISHED |
| Object | local historical and cultural designation |
—
|
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: local historical and cultural designation | Statement: [Cambrésis, currentUseOfName, local historical and cultural designation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentUseOfName Context triple: [Cambrésis, currentUseOfName, local historical and cultural designation]
-
A.
currentNameUsedFrom
Indicates that an entity’s currently used name has been in effect starting from a specified point in time or source.
-
B.
currentName
Indicates the present or most recently assigned name associated with an entity.
-
C.
nameUsedIn
chosen
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
D.
nameUsedBy
Indicates that a particular name is employed or referenced by a specific entity.
-
E.
currentCeremonialUseOfName
Indicates that a name is presently used in formal or ceremonial contexts, such as titles, rituals, or official occasions.
- 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_69ca8422ddf881908a3f8f876c9f53aa |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd0865a7108190b807afd259980db2 |
completed | April 1, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69cc7a5aeb748190afb89c6bbd2a6d6f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:35 p.m.