Triple
T7807721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multi-Day Passport |
E180597
|
entity |
| Predicate | validityPattern |
P32406
|
FINISHED |
| Object | consecutive days |
—
|
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: consecutive days | Statement: [Multi-Day Passport, validityPattern, consecutive days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validityPattern Context triple: [Multi-Day Passport, validityPattern, consecutive days]
-
A.
validityType
chosen
Indicates the specific kind or category of validity that characterizes how or under what conditions something is considered valid.
-
B.
hasValidity
Indicates that something possesses a period or condition during which it is considered legally, logically, or functionally acceptable or in force.
-
C.
validityArea
Indicates the geographic or contextual area within which something (such as a rule, document, or status) is considered valid or in effect.
-
D.
validIn
Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
-
E.
hasValidityPeriod
Indicates that something is associated with a specific time span during which it is considered valid or in effect.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae91687788190af9cb7aaa996d291 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:36 p.m.