Triple
T31672671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cook Islands passport |
E808312
|
entity |
| Predicate | hasExpiry |
P33304
|
FINISHED |
| Object | fixed validity period |
—
|
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: fixed validity period | Statement: [Cook Islands passport, hasExpiry, fixed validity period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExpiry Context triple: [Cook Islands passport, hasExpiry, fixed validity period]
-
A.
isExpired
Indicates that something has passed its valid time period or deadline and is no longer considered current or usable.
-
B.
canExpire
Indicates that the subject has the property or status of being able to end, lapse, or become invalid after a certain time or condition is met.
-
C.
hasValidityPeriod
chosen
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
-
D.
hasRemainingLifespan
Indicates that an entity still has a certain amount of time or capacity left before it reaches the end of its expected lifespan or usability.
-
E.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 30, 2026, 11:01 p.m.