Triple
T3300486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privilege Club |
E69317
|
entity |
| Predicate | statusValidity |
P32406
|
FINISHED |
| Object | 12 months |
—
|
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: 12 months | Statement: [Privilege Club, statusValidity, 12 months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusValidity Context triple: [Privilege Club, statusValidity, 12 months]
-
A.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
B.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
-
C.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
D.
validityType
chosen
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
E.
securityStatus
Indicates the current level or condition of protection, risk, or vulnerability associated with an entity or system.
- 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_69ad859e529c8190a404273f53cb487d |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0a66fcc819093931fe7a6507723 |
completed | March 8, 2026, 5:23 p.m. |
| PD | Predicate disambiguation | batch_69ada42407dc81909f60d7a14e1b7934 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:11 p.m.