Triple
T9290939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cambrésis |
E223513
|
entity |
| Predicate | wasEcclesiasticalPrincipality |
P87457
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Cambrésis, wasEcclesiasticalPrincipality, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEcclesiasticalPrincipality Context triple: [Cambrésis, wasEcclesiasticalPrincipality, true]
-
A.
endedAsPrincipality
Indicates that an entity’s existence or historical development concluded with it having the political status of a principality.
-
B.
wasPrinceBishopricUntil
Indicates that an entity functioned as a prince-bishopric up to (and including, or until) a specified point in time.
-
C.
hadPrincipality
Indicates that an entity possessed or governed a principality as its domain or territory.
-
D.
temporalPrincipalityRecognized
Indicates that an entity’s secular or political authority over a territory or domain is formally acknowledged or recognized, typically within a specific time frame.
-
E.
partOfHistoricalMonarchy
Indicates that an entity belonged to, was included within, or was under the authority of a specific historical monarchy.
- 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_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. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:35 p.m.