Triple
T7112091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T visa |
E165729
|
entity |
| Predicate | maximumDurationInitial |
P24237
|
FINISHED |
| Object | up to 4 years |
—
|
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: up to 4 years | Statement: [T visa, maximumDurationInitial, up to 4 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumDurationInitial Context triple: [T visa, maximumDurationInitial, up to 4 years]
-
A.
durationInitial
Indicates the initial length of time associated with an event, state, or process at its starting point.
-
B.
agingTimeMaximum
Indicates the maximum duration for which something is allowed or expected to age before it is considered expired, mature, or no longer valid.
-
C.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
D.
possibleDuration
chosen
Indicates the range or specific length of time that an action, event, or state can last or is allowed to last.
-
E.
maximumService
Indicates that an entity provides the highest allowable or achievable level of service within a given context 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_69c6888120f081908f8f01b201dc4a4c |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e5edf89c8190a069b35ff7768165 |
completed | March 27, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c4f9788190830288d00cc37026 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:43 p.m.