Triple
T5099594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Last Call Working Draft |
E114949
|
entity |
| Predicate | hasReviewPeriod |
P61096
|
FINISHED |
| Object | time-limited comment 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: time-limited comment period | Statement: [Last Call Working Draft, hasReviewPeriod, time-limited comment period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReviewPeriod Context triple: [Last Call Working Draft, hasReviewPeriod, time-limited comment period]
-
A.
areReviewedEvery
Indicates that one entity conducts reviews of another entity at every specified time interval or on every relevant occasion.
-
B.
hasAwardPeriod
Indicates the time span or date range during which an award is valid, active, or applicable.
-
C.
hasDiscoveryPeriod
Indicates the time span during which a particular discovery was made or recognized.
-
D.
canReview
Indicates that one entity has the permission or ability to evaluate, assess, or provide feedback on another entity.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- F. None of above. chosen
Provenance (4 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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7568e9c881909f114973faef6832 |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:40 p.m.