Triple
T22405454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comtat Venaissin |
E553867
|
entity |
| Predicate | hadSpecialPrivileges |
P6973
|
FINISHED |
| Object | tax exemptions |
—
|
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: tax exemptions | Statement: [Comtat Venaissin, hadSpecialPrivileges, tax exemptions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadSpecialPrivileges Context triple: [Comtat Venaissin, hadSpecialPrivileges, tax exemptions]
-
A.
hadSpecialStatusIn
chosen
Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
-
B.
formerPrivilege
Indicates that an entity once held a certain privilege or right but no longer does so in the present.
-
C.
hasSpecialMerit
Indicates that an entity possesses exceptional or noteworthy qualities that distinguish it from others in a positive way.
-
D.
lostPrivilegesDuring
Indicates that an entity had certain privileges revoked or suspended for the duration of a specified time period or event.
-
E.
hadMonopolyOnPower
Indicates that one entity exclusively controlled or dominated power or authority, without significant competition or sharing with others.
- 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_69e11e4da7048190b4387d422a9a0de5 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f158b739b88190a7f1f20fd1e9b188 |
completed | April 29, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e8989495bc81909d2699fce5992e28 |
completed | April 22, 2026, 9:44 a.m. |
Created at: April 16, 2026, 8:46 p.m.