Triple
T4205100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 106th United States Congress |
E86163
|
entity |
| Predicate | concurrentResolution |
P47102
|
FINISHED |
| Object | Y2K preparedness measures |
—
|
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: Y2K preparedness measures | Statement: [106th United States Congress, concurrentResolution, Y2K preparedness measures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concurrentResolution Context triple: [106th United States Congress, concurrentResolution, Y2K preparedness measures]
-
A.
concurrentModel
Indicates that two or more processes, activities, or states occur or are valid at the same time, potentially interacting or overlapping in execution.
-
B.
resolves
Indicates that one entity successfully finds a solution, answer, or outcome for a problem, conflict, or uncertainty involving another entity.
-
C.
requiresConcurrenceWith
Indicates that one action, decision, or condition must be agreed upon or approved by another specified party or entity before it can proceed or be valid.
-
D.
heldConcurrentlyWith
chosen
Indicates that two or more events, roles, or states occurred or were in effect at the same time.
-
E.
resolvedIn
Indicates that an issue, conflict, or process is brought to a conclusion or solution within a specified context, medium, or timeframe.
- 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_69aed93b89f48190a31f6d57c760e42f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0382eafc8190946bf45bf28095dd |
completed | March 9, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69af01959c4881909eb1adcb3bdadbe6 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:49 p.m.